Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

turf_door_counts

Read-onlyIdempotent

Retrieve door and people counts for saved lists by folder, including folder totals, to help organizers plan canvassing coverage.

Instructions

Doors and people per saved list (turf) in a folder, with folder totals. With no folder, every folder.

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

Input Schema

NameRequiredDescriptionDefault
folder_idNoFolder ID from list_folders
folder_nameNoPart of a folder name, e.g. Northside

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive operation, so the safety bar is covered. The description adds useful behavior beyond that: results are aggregated per saved list with folder totals, and omitting the folder widens scope to all folders. It does not disclose what happens when folder_name matches multiple folders or when both filters are given.

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?

Two short sentences, front-loaded with what is returned and followed by the scope default; every word carries weight. The terseness flirts with ambiguity ('Doors and people') rather than wasted text.

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, return-value explanation is unnecessary, and annotations cover the safety profile, so the remaining burden is small. Still, for a two-filter aggregation tool the definition should clarify filter precedence and what 'doors' and 'people' count, which it does not.

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 description coverage is 100%, with folder_id sourced from list_folders and folder_name described as a partial match with an example, so the schema does the heavy lifting. The description only reinforces the default-scope behavior; it adds no interpretation of the partial-match semantics or filter precedence.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and grouping ('Doors and people per saved list (turf) in a folder, with folder totals'), which is distinctive against the sibling list (no other tool deals with turf door counts). However, it omits a verb ('returns'/'counts') and the telegraphic phrasing 'Doors and people' leaves it ambiguous whether these are distinct-door and distinct-person counts or knock/contact totals.

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?

The clause 'With no folder, every folder' gives an explicit rule for the no-argument case, which is genuine usage guidance. It says nothing about choosing between folder_id and folder_name when both are supplied, nor points to list_folders for obtaining an ID — that link only appears inside the schema.

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