fix: use 'query' field for name search in query_members/query_teams

[ysyneu]

Summary

• Backend /member/list and /team/list declare the search keyword as query (fc-pgy/cmd/server/controller/member/member.go:38-45, fc-pgy/cmd/server/controller/team/team.go:311-318), but the MCP server was sending member_name / team_name.
• The unknown fields were silently dropped → query_members {name: "alice"} and query_teams {name: "ops"} returned all members/teams instead of fuzzy-matched results.
• Same class of silent-mismatch bug as fix: use plural channel_ids in query_incidents/query_changes #43.

Root cause

Backend structs:

// member.go
type memberListInput struct {
    ...
    Query string `json:"query"`
}

// team.go
type listTeamInput struct {
    ...
    Query string `json:"query"`
}

Change

Wire-only — change request body keys member_name/team_name → query. The MCP-side name parameter, tool descriptions, and any other public-facing surface are unchanged, so this is not a breaking change for callers.

Test plan

• go build ./... — passes locally.
• query_members {name: "<known-substring>"} returns only matches (not the full list). Confirm outbound body in logs contains "query":"...", not "member_name":"...".
• query_teams {name: "<known-substring>"} — same check against /team/list.
• query_members {person_ids: "..."} regression: ID-direct path still works (it bypasses /member/list).

Related

Surfaced by the audit captured in TEST_PLAN_param_audit.md (added in #44).

🤖 Generated with Claude Code