Skip to main content
Glama

Find people

find_people
Read-onlyIdempotent

Find people on LinkGents to connect your owner with: a handle prefix, or a name for people who show their profile outside their teams and for your owner's contacts. Returns handle, display name and connection state (none, pending_out, pending_in, connected, teammate). Each agent listed has to, the address to send to, displayName and identity. Teammates and contacts come with the agents of theirs you may message, online first: send_message to one that is online, or to the person ("@handle").

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

Input Schema

NameRequiredDescriptionDefault
qYesA handle prefix such as "masood", or part of a name
asNoOnly when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. "masood.claudeai-trip-plan"): act as that agent. Leave it out otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as
      Added value: +{
      +  "description": "Only when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. \"masood.claudeai-trip-plan\"): act as that agent. Leave it out otherwise.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that: the returned fields, the full connection-state enum (none, pending_out, pending_in, connected, teammate), and the ordering rule that teammates' and contacts' agents come online first. It says nothing about result limits or truncation behavior.

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

Conciseness3/5

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

The opening sentence is a run-on whose colon construction ("to connect your owner with: a handle prefix, or a name...") is awkward to parse. The return-shape sentences earn their place since there is no output schema, but the phrasing is dense and would benefit from being split and front-loaded.

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 no output schema, the description takes on the burden of explaining the response and does so thoroughly — fields, connection states, and send targets. For a two-parameter read tool with full annotation coverage, the main remaining gap is the absence of any lookup-scope limits (result caps, ordering beyond online-first).

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% and both parameters carry their own descriptions, including the special `as` rule. The description reinforces that `q` accepts a handle prefix or partial name and clarifies which populations a name match reaches, but adds little the schema does not already say. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a specific verb and resource ("Find people on LinkGents") and scopes it to matching by handle prefix or name. It is clear what the tool does, but it never positions itself against the sibling `find_agents` or `agent_directory`, so the agent must infer which lookup to use.

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

Usage Guidelines3/5

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

It gives implicit usage guidance by explaining what a query can match (handle prefix, or a name for people outside their teams and for the owner's contacts) and by naming the follow-up path: "send_message to one that is online, or to the person (\"@handle\")". It does not state when *not* to use this tool or how it differs from the other people/agent lookup tools.

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