Menu

#51 member_detail: accept member name as well as UUID

closed
nobody
None
2026-04-05
2026-04-03
Anonymous
No

Originally created by: kumaakh

Currently member_detail only accepts a UUID as member_id. Calling it with a friendly name like focus-dev1 returns "Member not found", requiring a prior list_members call to look up the UUID.

Proposed change

Accept either UUID or member name in member_id. If the value doesn't parse as a UUID, treat it as a name lookup.

Benefit

Removes a round-trip when the PM or user already knows the member name.

Related

Tickets: #65

Discussion

  • Anonymous

    Anonymous - 2026-04-05

    Ticket changed by: kumaakh

    • status: open --> closed
     
  • Anonymous

    Anonymous - 2026-04-05

    Originally posted by: kumaakh

    Closed based on live testing against v0.1.3_d10302:

    • member_detail(member_name="focus-dev2") → correct member returned
    • member_detail(member_name="nonexistent-member") → "Member not found."
    • member_detail() (no params) → "provide either member_id or member_name"
    • member_detail(member_id="...", member_name="focus-dev1") → member_id took precedence (focus-dev2 returned)

    member_name is supported on all member tools via the memberIdentifier Zod spread in resolve-member.ts.

     

Log in to post a comment.

MongoDB Logo MongoDB