Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

contact_history_summary

Read-onlyIdempotent

Counts contact attempts for up to 25 people by contact type, outcome, and survey responses, optionally since a date, to summarize outreach history.

Instructions

Counts of contact attempts for up to 25 people: by contact type (phone, walk, text), by result (canvassed, not home, refused...) and survey responses recorded.

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": {
      "van_ids": "<van_ids>"
    },
    "name": "contact_history_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly count attempts on or after this date
van_idsYesVAN IDs from search_people, up to 25

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive, so safety is covered. The description adds aggregation semantics (counts grouped by type and result) but says nothing about behavior beyond the batch limit, such as what happens with unknown or duplicate VAN IDs or how missing contact history is represented.

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 dense sentence that front-loads the core operation and enumerates the breakdown dimensions; there is no filler. Minor loss from the awkward line-wrapped formatting and the open-ended 'refused...' ellipsis.

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 values need not be explained, and the read-only profile is covered by annotations. What remains missing is guidance on where this fits among the several other summary tools and any caveats about batch size or empty results, leaving the definition only minimally sufficient.

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 100%, so both parameters and their meanings are fully documented in the schema. The description only reinforces the 25-ID cap already stated for van_ids and adds nothing about the 'since' date filter's semantics.

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 verb and resource: counting contact attempts for a set of people, broken down by contact type, result, and survey responses. That is concrete enough to distinguish it from person-level tools like get_person or list_events, though it never names a sibling summary tool it is not.

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: the 'up to 25 people' framing and 'VAN IDs from search_people' hint at the lookup-then-summarize workflow. There is no explicit when-to-use or when-not-to-use guidance, and no mention of how this differs from turf_door_counts or event_signups_summary.

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