Skip to main content
Glama
Sign In
civicgraph-mcp

civicgraph-mcp

by cstillick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

entity_profile

Summarizes all known data about an entity, including aliases, sources, and connections to donations, lobbying, and contracts, each with provenance.

Instructions

Everything we know about an entity: aliases, sources, and its edges (donations, lobbying, contracts) summarized by type, each with provenance.

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

Input Schema

NameRequiredDescriptionDefault
entity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so the description must carry the behavioral disclosure burden. It does not mention whether the operation is read-only, if it requires special permissions, or any performance implications. The focus is on content, not behavior.

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, well-structured sentence that front-loads the purpose ('Everything we know about an entity') and follows with specific contents. No wasted words.

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?

The description outlines the tool's output (aliases, sources, edges) but lacks specifics on return format, pagination, or limits. Without an output schema, more details would help, though the summary is adequate for basic use.

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?

The only parameter 'entity_id' is not described in the tool description. With 0% schema description coverage, the description should compensate but it does not. However, the parameter name and required nature make its purpose somewhat clear, meriting a score of 3.

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?

The description clearly states it provides 'everything we know about an entity' including aliases, sources, and edges summarized by type with provenance. This is a specific verb-resource combination that distinguishes it from siblings like 'connections' or 'resolve_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?

Implied usage: use when you need a comprehensive profile of an entity. However, it does not explicitly state when not to use it or provide comparisons to sibling tools, leaving some ambiguity.

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