Skip to main content
Glama

Get a person

naut_get_person
Read-only

One person, their companies, and their coworkers. Accepts an id or a slug. Costs 5 credits.

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": {
      "id": "<id>"
    },
    "name": "naut_get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPerson id or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint=true and openWorldHint=false, so the description is not obligated to cover safety. It does add genuinely new behavioral facts: the record is enriched with companies and coworkers, and the call consumes 5 credits — a cost signal an agent needs before spending budget, and one that pairs usefully with not-found or rate-limit reasoning. It stops short of 5 because it says nothing about failure behavior or what happens when the id is invalid.

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?

Three short sentences with zero filler, and the payload scope is front-loaded before the identifier rule and the cost. The opening is a bare noun phrase with no verb, so it reads as a fragment, but that is a style quibble rather than wasted space.

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 one-parameter read tool with a fully documented schema and annotations, the description covers the essentials: what comes back, what input is accepted, and what it costs. The notable gap is whether this call exposes contact details (which would distinguish it from naut_reveal_contact) and how it behaves on an unknown id; without an output schema, the description is the only place those could be stated.

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 100% and the single parameter's schema text already reads "Person id or slug." The description's sentence restates exactly that, adding no format, example, or lookup guidance. Baseline 3 is correct where the schema does all the work.

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 resource and its return scope: a single person plus that person's companies and coworkers, resolved by id or slug. That clearly separates it from the search_* siblings (which return lists) and from naut_me (which is the caller's own record). It falls short of 5 because it never explicitly contrasts itself with naut_reveal_contact or naut_search_people, leaving the reader to infer the boundary.

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?

"Accepts an id or a slug" implies you must already hold an identifier, which hints that search_people is the discovery path, but this is never stated. There is no explicit when-to-use, when-not-to-use, or named alternative, so routing guidance is inferred rather than given.

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