Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

canvass_codes

Read-onlyIdempotent

Fetch valid result codes and contact types, including Not Home, Refused, Phone, Walk, and SMS, to standardize canvassing data entry and reporting.

Instructions

Result codes (Not Home, Refused, Wrong Number...) and contact types (Phone, Walk, SMS).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds modest context by naming the actual code values the caller will encounter, which helps interpretation. It says nothing about caching, ordering, or whether the set is static, but those gaps are minor for a safe zero-argument lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is a single short fragment with no wasted words, so it is certainly concise. But the terseness costs clarity: without a leading verb or a statement of what is returned, the sentence reads like a label rather than a definition, and there is no front-loaded statement of purpose.

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?

Complexity is low — zero parameters and an output schema that documents the return shape, so the description need not explain return values. Even so, the definition never states what the tool does with these codes, leaving a reader unable to tell whether it is a reference-data endpoint or a computation. For such a simple tool it is close to adequate but not complete.

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?

The tool takes no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not mislead about inputs.

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 resources it concerns — result codes (with concrete examples like Not Home, Refused, Wrong Number) and contact types (Phone, Walk, SMS). However, it is a noun fragment with no verb: it never states whether the tool lists, retrieves, or maps these codes, and it does not distinguish itself from the sibling list_activist_codes, which by name alone could overlap. The agent can guess it is a lookup but must open the schema to confirm.

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

Usage Guidelines2/5

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

There is no guidance on when to call this tool, no prerequisites, and no mention of alternatives such as list_activist_codes. The agent is left to infer that this should be used before interpreting canvass results, but that inference is not supported by any sentence in the definition.

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