Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

person_signups

Read-onlyIdempotent

Lists all event shifts a person signed up for, with role and status, when given their VAN ID.

Instructions

Every event shift one person has signed up for, with role and status.

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

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description's added value is limited to stating that results carry a role and a status per shift; it says nothing about ordering, pagination, or whether past versus upcoming shifts are included.

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?

One short sentence, front-loaded with the resource and finished with the fields returned. There is no filler, hedging, or redundant restatement of the tool name.

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?

This is a simple single-parameter read whose annotations and output schema carry the safety and return-value burden, so the description only needs to pin down scope, which it does. Minor gaps remain on whether results are time-bounded or ordered, but nothing essential to invoking it correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema coverage, the schema already explains that van_id is the person's VAN ID sourced from search_people and must not be guessed. The description contributes only the phrase 'one person', which restates the same meaning rather than adding format, range, or lookup context.

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 ('every event shift one person has signed up for') and the fields returned ('role and status'), so the agent knows this is a per-person signup listing, not an event roster or a summary. It does not explicitly differentiate itself from the sibling event_signups_summary, which is the only thing keeping it from a 5.

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 is only implied through scope: 'one person' signals that this tool is for drilling into an individual's signups after identifying them, and the schema reinforces that van_id must come from search_people. There is no explicit when-to-use or when-to-prefer-an-alternative statement, and no mention of how this differs from event_signups_summary.

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