Skip to main content
Glama

Reveal a person's contact details

naut_reveal_contact
Idempotent

Reveal a person's telegram, email, phone and LinkedIn. A permanent unlock: later calls on the same person cost the basic rate. Needs the read:contacts scope. Costs 10 credits the first time, then 5.

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_reveal_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPerson id or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Adds real behavior beyond the annotations: the unlock is permanent so repeat calls on the same person bill at the basic rate, the call requires the read:contacts scope, and the credit charge is 10 the first time and 5 thereafter. That also reconciles the unusual annotation pair readOnlyHint=false with idempotentHint=true, explaining the side effect (credit spend and unlock) alongside stable results.

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?

Three short sentences, front-loaded with what is revealed, then the unlock and cost terms, then the scope requirement. No filler and every sentence carries decision-relevant information.

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?

Without an output schema, the description usefully enumerates the four contact channels returned, and cost/scope are covered. It stops short of saying what happens when a channel is unavailable or the person has no contacts, which matters for a paid single-record fetch.

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?

Only one parameter and the schema already documents it as 'Person id or slug' at 100% coverage. The phrase 'the same person' hints that id identity persists across calls, but no format, slug syntax, or resolution fallback is added beyond the schema.

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?

Specific verb plus resource plus exactly which fields are disclosed: telegram, email, phone and LinkedIn. That enumeration distinguishes it from sibling lookups like naut_get_person or naut_search_people, which an agent can assume do not return contact channels.

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?

Usage context is implied rather than stated: the tool is the one that surfaces contact channels, and the description notes the scope requirement and the one-time vs repeat pricing. It never explicitly says when to prefer this over naut_get_person or what to do if the person is unknown, so guidance is present but inferential.

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