Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

search_people

Read-onlyIdempotent

Find people in VAN by first or last name, city, or ZIP code; returns VAN IDs, names, cities, and total match count.

Instructions

Find people by name, city or ZIP. Returns VAN IDs, names and cities, plus the total match count. Searching by phone number or email is not offered.

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
cityNoCity of the home address
limitNo
zip_codeNo5-digit ZIP of the home address
last_nameNoLast name or its start
first_nameNoFirst name or its start

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds result shape and the total match count, but says nothing about the limit parameter's effect (default 10, max 25) or how truncation interacts with the match count — a meaningful behavioral gap for a search tool.

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?

Two sentences, searchable criteria and return shape first, the negative constraint last. Every clause carries information an agent would otherwise have to guess.

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?

An output schema exists, so explaining return fields is mild redundancy, but the total match count and the phone/email exclusion are genuinely useful framing. The only real omission is guidance on the limit/pagination ceiling against a potentially larger result set.

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 80% and the schema already documents first/last name prefix matching, 5-digit ZIP and city. The description adds no parameter-level detail beyond restating the three searchable fields, and never mentions the limit control. Baseline 3 applies.

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 ('Find people') plus the searchable dimensions (name, city, ZIP) and result fields. It doesn't explicitly differentiate from the sibling get_person (single-record lookup) or person_signups, so it falls short of 5.

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

Usage Guidelines4/5

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

Gives clear positive context (search by name, city or ZIP) and an explicit exclusion ('Searching by phone number or email is not offered'), which prevents a common misfire. It stops short of naming an alternative for ID-based lookup or explaining what to do when no criteria are supplied.

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