Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

event_signups_summary

Read-onlyIdempotent

Summarize event or shift signups with counts by status, committed totals, and roster details so organizers can review who is attending.

Instructions

Who is signed up for an event or one of its shifts: counts by status, how many are committed, and the roster (names as the privacy policy allows, role, 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": {
      "event_id": "<event_id>"
    },
    "name": "event_signups_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
shiftNoShift name (e.g. Morning) or shift ID
event_idYesThe event's ID from list_events
include_rosterNo

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: roster names are redacted as the privacy policy allows, and the output is a mixture of aggregate counts plus a roster rather than a raw list. It stops short of saying whether the roster is truncated or capped, which would have completed the picture.

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?

One front-loaded sentence that names the subject ('who is signed up') before enumerating the outputs. The nested parenthetical in the roster clause is slightly dense but every clause carries information. No filler or 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?

With an output schema present, the description needn't explain return values, and annotations cover the safety profile, so the remaining burden is scope and semantics. It covers scope (event or one of its shifts), content (counts by status, committed count, roster) and a privacy caveat. Minor gaps remain around the meaning of 'committed' and roster size limits.

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 67%, with event_id and shift documented in the schema itself and only include_roster undocumented. The description's reference to 'the roster (names as the privacy policy allows, role, status)' hints at what include_roster governs, but never states that setting it false suppresses the roster and returns counts only. That is a marginal gain over the schema, matching the baseline for this coverage level.

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 gives a specific verb-and-resource shape: it returns signup counts by status, a committed count, and a roster for an event or one of its shifts. That is enough to separate it from a per-person view like person_signups, though the sibling is never named explicitly. The scope (event-level, optionally shift-scoped) is clear.

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: an agent can infer this is the tool for 'how many / who is signed up for this event' rather than for a person's history. There is no explicit when-to-use versus when-not statement and no mention of prerequisites, even though list_events appears as a referenced source of event_id. The reader must connect the dots from the description alone.

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