Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

list_events

Read-onlyIdempotent

Retrieve events scheduled between two inclusive dates, including their shifts and locations, to plan canvassing, phone banks, or trainings by date range.

Instructions

Events starting between two dates (inclusive), with their shifts and locations.

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": {
      "start_date": "<start_date>"
    },
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast day to include. Leave it out and only start_date is searched, so set it for a week or a weekend
event_typeNoCanvass, Phone Bank, Training...
start_dateYesA date like 2026-10-19

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 safety is covered. The description usefully adds that results are bundled with shifts and locations, and that bounds are inclusive, but says nothing about ordering, result caps, or whether canceled events 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the payload note is appended efficiently. It is arguably too short given the absence of any usage guidance, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and full parameter descriptions, the description does not need to explain return shapes. It is still thin on operational details an agent would want, such as ordering, limits on result size, and behavior for very wide date windows.

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

Parameters4/5

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

Schema coverage is 100%, so 3 is the baseline, but the description adds real meaning the schema lacks: matching is on event start dates and both bounds are inclusive, which resolves ambiguity about overlap versus start-date filtering that the schema's "A date like 2026-10-19" does not.

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 resource (events), the filter (starting between two dates), and the payload (with their shifts and locations). It is clear enough to distinguish from the other list_* siblings, though it never names an alternative to route against.

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 by the filter: call it when you need events in a date window. There is no explicit when-not guidance, no mention of related tools like the signups or summary siblings, and no statement about what happens when the range is wide.

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