Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

list_activist_codes

Read-onlyIdempotent

Retrieve activist codes available in a committee, with optional filters for code name prefix, code type (e.g., Volunteer), and archived status.

Instructions

Activist codes available in this committee.

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

Input Schema

NameRequiredDescriptionDefault
nameNoStart of the code name
code_typeNoe.g. Volunteer
include_archivedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/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 safety is covered structurally. The description adds nothing beyond that: it says nothing about whether archived codes are excluded by default, how filtering interacts, or what volume of results to expect. With annotations carrying the safety profile, the description's marginal contribution is essentially zero.

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 waste, but that brevity comes at the cost of substance rather than being earned conciseness. There is no front-loaded structure beyond the bare resource name.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but for a filtered list tool with three parameters and several similar siblings the definition leaves the agent without scoping, filtering, or exclusion semantics. The description does not do enough work for the tool's role in the catalog.

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?

Schema coverage is 67% — name and code_type carry descriptions ('Start of the code name', 'e.g. Volunteer'), but include_archived has none. The description supplies no additional parameter meaning, notably leaving the default exclusion of archived codes and the prefix-matching behavior of 'name' unexplained beyond the bare schema text.

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 sentence identifies the resource (activist codes) and a scope (this committee), but it is a noun phrase rather than a stated action, and it does not distinguish this tool from sibling listers such as person_activist_codes or canvass_codes. An agent can guess it enumerates codes, but nothing in the text confirms it versus retrieving them for a specific person.

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 when-to-use guidance, no prerequisites, and no mention of any alternative. Given siblings like person_activist_codes and canvass_codes exist, the absence of any routing information forces the agent to infer selection from the name alone.

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