Skip to main content
Glama

Coline

Find people

find_people
Read-onlyIdempotent

Use this to look up teammates by name or email before assigning a task or inviting someone. Returns names and email addresses of people in the workspace.

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": {
      "workspace": "<workspace>"
    },
    "name": "find_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoPart of a name or email. Omit to list everyone.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
peopleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered elsewhere. The description adds the return shape (names and email addresses), which is useful, but says nothing about match behavior, pagination, or what happens when nothing matches.

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?

Two short sentences, no redundancy, with the purpose and the use case front-loaded and the return value closing it out. Nothing in the text is filler.

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

Completeness4/5

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

With an output schema present, the description need not explain return values in depth, and annotations cover the safety profile, so this is close to complete for a three-parameter read tool. The remaining gap is practical calling detail — what limit does and how matching behaves — which the agent must infer.

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 67%: query and workspace are already documented in the schema, including the "omit to list everyone" behavior. The description reinforces the name/email lookup intent but adds no meaning to the undocumented limit parameter or to matching semantics such as partial vs exact match.

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

Purpose4/5

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

"Look up teammates by name or email" gives a specific verb (look up) and resource (teammates), and adds what comes back: names and email addresses. It does not name or distinguish itself from any sibling lookup tool, so it falls short of a 5.

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

Usage Guidelines4/5

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

The description anchors usage to concrete moments — before assigning a task or inviting someone — which tells the agent when this call is appropriate. It offers no exclusions or named alternatives for people-lookup, so it stops at clear context rather than full routing guidance.

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.

Resources