Skip to main content
Glama
Sign In
civicgraph-mcp

civicgraph-mcp

by cstillick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

connections

Retrieve neighboring entities within a specified number of hops, optionally filtered by relationship types such as donations, lobbying, contracts, employment, or affiliations.

Instructions

Neighboring entities within hops, optionally filtered to edge types (donated_to, lobbied_for, contracted_with, employed_by, affiliated_with).

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_id": "<entity_id>"
    },
    "name": "connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYes
hopsNo
typesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior. It reveals hop distance and filtering by types, but does not specify whether all neighbors are returned at once, ordering, or performance characteristics. The behavior is partially transparent but not fully detailed.

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?

A single, concise sentence of 19 words that efficiently conveys the core functionality. No unnecessary words, and the main action is front-loaded.

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?

Given the tool has 3 parameters and no output schema or annotations, the description provides a reasonable overview but lacks details on output and parameter descriptions for entity_id. It is somewhat incomplete for a graph traversal tool.

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 0%, so the description must explain parameters. It explains 'hops' and 'types' (listing allowed values), but does not describe 'entity_id' at all. The explanation of 'types' is basic and doesn't clarify array format.

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?

The description clearly indicates the tool retrieves neighboring entities within a given number of hops, optionally filtered by edge types. However, it does not explicitly state the output format or use a strong verb like 'get' or 'retrieve'.

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 description implies usage for exploring connections, but provides no explicit guidance on when to use this tool versus siblings like path_between or entity_profile. No exclusion criteria or alternatives are mentioned.

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