Skip to main content
Glama

search_people

Read-only

Finds the people of the project whose name, role or id CONTAINS the text (case and accents ignored; a substring match, not a fuzzy one). Returns light rows {id, name, role, color}; an empty results list (not an error) when nothing matches. Read-only. It resolves a person's id for update_person, assign_person, unassign_person and delete_person; the blocks a person is assigned to are read with get_cell_details (per block) or get_full_data (whole schema).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesText to search for in the name, the role or the id (substring, case and accents ignored)
expectedProjectIdNoUUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Text to search for in the name or the role"New value: +"Text to search for in the name, the role or the id (substring, case and accents ignored)"
  2. Changed2 schema fields changed
    • changedInput schema / properties / expectedProjectId / description
      Previous value: -"UUID du projet visé par CET appel. Cible RÉELLEMENT ce projet au lieu du projet de session. Refusé sans rien modifier si l'accès n'est pas accordé."New value: +"UUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted."
    • changedInput schema / properties / query / description
      Previous value: -"Texte à chercher dans le nom ou le rôle"New value: +"Text to search for in the name or the role"
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond readOnlyHint by disclosing the matching semantics (substring, not fuzzy; case/accent insensitive), the return shape ({id, name, role, color}), and that an empty results list is not an error. Those details materially affect how the agent interprets and retries calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences, front-loaded with what is searched and how matching works, followed by return/empty behavior and routing hints. Every sentence carries actionable information; none is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return shape and empty-result behavior itself, and the two-parameter schema is fully documented. An agent has everything needed to call and interpret this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, including expectedProjectId's targeting and access-refusal behavior. The description reinforces the query's substring semantics but adds little beyond the schema's own parameter descriptions. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Finds the people of the project') and defines the search surface precisely: name, role or id, substring, case and accents ignored. This is clearly distinguishable from sibling search tools like search_cells.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this tool to resolve a person's id for update_person, assign_person, unassign_person and delete_person, and use get_cell_details or get_full_data for block assignments. The alternatives and their conditions are named directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.