Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

get_person

Read-onlyIdempotent

Retrieves a person's name, city, and contact-info availability (yes/no and SMS opt-in) using a VAN ID from search_people, without exposing contact values.

Instructions

One person's name, city and what contact info is on file (yes/no and SMS opt-in), never the values.

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": {
      "van_id": "<van_id>"
    },
    "name": "get_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
van_idYesThe person's VAN ID, from search_people. Never guess one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value by disclosing a privacy constraint the schema cannot express: contact info is returned as yes/no and SMS opt-in only, never the underlying values. It does not state what happens when a van_id matches no person, which is the remaining behavioral gap.

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?

A single sentence with no wasted words, and the most important constraint ('never the values') is placed at the end for emphasis. The phrasing is slightly elliptical — the field list runs together — but it stays tight 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?

For a one-parameter read tool with an output schema and full annotation coverage, this is nearly complete: it explains the payload shape, the privacy constraint, and where the ID comes from. The only omission an agent would notice is error/empty-result behavior when the VAN ID is unknown.

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 the sole parameter already carries a strong description ('The person's VAN ID, from search_people. Never guess one.'). The tool description adds nothing about the parameter, so the baseline 3 applies — the schema does all the work here.

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 the resource (a single person) and enumerates exactly what comes back: name, city, and presence/opt-in flags for contact info. That field list distinguishes it from siblings like contact_history_summary or person_signups without needing to name them. It lacks an explicit verb ('returns'/'fetches'), reading as a sentence fragment rather than a statement of action.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative is named despite search_people being an obvious neighbor. The clause 'never the values' implicitly signals the intended use case — checking whether contact info exists without exposing PII — but the agent must infer that. Adequate but leaves routing decisions to the caller.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.