Skip to main content
Glama
Sign In
civicgraph-mcp

civicgraph-mcp

by cstillick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

path_between

Find the shortest sourced path connecting two entities through campaign donations, lobbying, and government contracts, revealing money and influence links.

Instructions

Shortest sourced path between two entities — how the money/influence connects them across donations, lobbying, and contracts.

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": {
      "entity_a": "<entity_a>",
      "entity_b": "<entity_b>"
    },
    "name": "path_between"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_aYes
entity_bYes
max_hopsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. Only states 'shortest sourced path' without disclosing behavior like cost, limits, or whether it's read-only. Lacks important context for agent decision-making.

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

Conciseness5/5

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

Single sentence that is front-loaded with verb and core purpose. No wasted words; every part adds value.

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?

Given no output schema and no annotations, the description is incomplete. It lacks parameter explanations, output format, and any constraints or nuances (e.g., what 'sourced' means, types of connections). Minimal context for a tool with 3 parameters.

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

Parameters1/5

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

Schema description coverage is 0%, and description adds no explanation for any of the 3 parameters (entity_a, entity_b, max_hops). The default for max_hops (4) is not explained. Agent receives no help understanding parameter semantics.

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

Purpose5/5

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

Description clearly states verb (finds), resource (shortest sourced path between two entities), and scope (money/influence connections). Distinguishes from siblings like 'entity_profile' which focuses on a single entity.

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?

Implies usage for finding shortest path in network, but no explicit guidance on when to use this vs siblings like 'connections' or 'graph_stats'. No contraindications provided.

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

Deploy Server

Other Tools