Skip to main content
Glama

Search people

naut_search_people
Read-only

Search and filter people. Supports q, roles, channels, contactType, sort. Costs 5 credits.

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": "naut_search_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText to match against names, handles and job titles.
pageNoPage number, from 1.
sortNo
limitNoRows per page, 1 to 100. Default 30.
rolesNoComma-separated role buckets, e.g. founder,executive.
channelsNoComma-separated channels the person must have: twitter,telegram,email,phone.
contactTypeNoanalyst = analyst-verified records only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false. The description adds a genuinely useful behavioral detail, "Costs 5 credits," but does not explain result shape, pagination behavior, or practical limits.

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?

The description is two short, front-loaded sentences with no filler. Listing parameter names repeats structured schema information and is the only mildly wasteful element.

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

Completeness3/5

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

For a seven-parameter search tool with no output schema, the definition covers cost and supported filters but leaves gaps around result contents and how to choose between this and sibling search/get tools. The schema handles most parameter detail, making the definition adequate but not complete.

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 description coverage is high at 86%, so the schema already documents most parameters well. The description lists supported filters (q, roles, channels, contactType, sort) but adds no syntax, defaults, or constraints beyond what the schema provides.

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?

States a specific verb and resource: "Search and filter people." This clearly distinguishes it from sibling tools focused on investors, projects, or services, though it does not explicitly differentiate it from the generic naut_search sibling.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives such as naut_search or naut_get_person. Usage is only implied by the tool name and the phrase "Search and filter people."

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