Skip to main content
Glama

Search people

search_people
Idempotent

Find people at firms in the Corridome register by name, title or firm, narrowed by kind of firm, state and kind of published contact. One of name, title or firm_id is required: firm_kind, state and with_contact only narrow a search, so a request for everyone, or everyone with an email, has no search to run and is answered in words (ask which firm, title or name). Returns each person's id, name, title and firm, the kind of document that states their title, and which kinds of contact are published. With include_contacts, it also returns their published business contacts, using one credit from the account's monthly allowance for each contact opened.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameNoPart of the person's name.
pageNoWhich page of results, from 1.
limitNoHow many results to return, 1 to 50.
stateNoThe US state of their firm's main office, as a two-letter code.
titleNoPart of a title they hold, such as "partner" or "managing director".
firm_idNoOnly people at this firm: its id from search_firms, or its corridome.com address.
firm_kindNoThe kind of firm they work at. adviser: investment advisers registered with the SEC, and exempt reporting advisers. broker-dealer: registered broker-dealers. other: firms known from their own websites and filings.
with_contactNoOnly people with this kind of published contact: email, phone, or any (LinkedIn included). It narrows a search by name, title or firm_id and is never a search on its own.
include_contactsNoAlso return each person's published business contact (email, phone, LinkedIn profile). Each contact opened uses one credit from the account's monthly allowance; a person with no contact, a contact that is only a LinkedIn profile, or one already opened this month uses none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / with_contact / description
      Previous value: -"Only people with this kind of published contact: email, phone, or any (LinkedIn included)."New value: +"Only people with this kind of published contact: email, phone, or any (LinkedIn included). It narrows a search by name, title or firm_id and is never a search on its own."
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, which is consistent with the description's disclosure that include_contacts consumes credits from a monthly allowance — a side effect that justifies the non-read-only flag. The description adds real value here: which contacts cost a credit (not ones already opened this month, not LinkedIn-only ones) and the exact fields returned. It is a genuinely informative disclosure, though it does not state error behavior or what happens when the allowance is exhausted.

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

Conciseness4/5

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

Front-loaded with the core action, followed by the constraint, the return shape, and the credit caveat in a logical order. Every sentence carries information, though the narrowing point is made twice ("narrowed by kind of firm, state and kind of published contact" then again in the required-parameter sentence), which slightly inflates length.

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?

Nine parameters with no output schema, yet the description enumerates what is returned (id, name, title, firm, source document kind, published contact kinds) and what include_contacts adds. Combined with the requirement rule and the credit model, an agent has everything needed to call correctly and decide when not to call.

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

Parameters4/5

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

Schema coverage is 100%, so the per-field meanings are already documented and the baseline would be 3. The description earns an extra point by stating a cross-parameter constraint the schema cannot express: exactly one of name/title/firm_id must be present, and with_contact/firm_kind/state only narrow. It also reiterates the credit cost of include_contacts where the schema only mentions it once, which is the highest-stakes parameter.

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 ("Find people at firms in the Corridome register") plus the three searchable axes (name, title, firm) and the three narrowing filters. The resource (people) and the firm_id reference to search_firms make it distinguishable from the sibling search_firms/get_firm tools without opening a schema.

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 declares a hard precondition (one of name, title or firm_id is required) and explains that firm_kind, state and with_contact are narrowers only. It goes further to describe the negative case — "a request for everyone, or everyone with an email, has no search to run and is answered in words (ask which firm, title or name)" — which tells the agent what to do instead of calling.

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