Skip to main content
Glama
Sign In
pushbuild-mcp

pushbuild-mcp

Official
by pushbuild
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search APIs

search_apis
Read-only

Find public-data APIs by keyword and return matching API IDs with coverage details, no key required. Use it to identify Pushbuild APIs for topics like campaign finance, inspections, or SEC filings.

Instructions

Find Pushbuild data APIs by keyword (e.g. 'campaign contributions texas', 'restaurant inspections', 'sec 13f'). Returns API ids and what each covers. No key needed.

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": {
      "query": "<query>"
    },
    "name": "search_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10).
queryYesKeywords.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds two pieces of context the annotations do not: that results are API ids with coverage summaries, and that no authentication key is required — a genuinely useful operational detail.

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?

Three short sentences, no filler. The core action is front-loaded, the examples directly support query formulation, and the auth caveat closes it out.

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

Completeness4/5

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

For a two-parameter read-only search tool, the description covers what it does, what it returns, and the auth situation. Minor gaps remain around result ordering/relevance and whether results are paginated, but nothing essential to invoking it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the three example queries meaningfully clarify that 'query' accepts free-text keyword combinations mixing topic and geography rather than exact API names. That is real added meaning beyond 'Keywords.'; only 'limit' behavior is left entirely to the schema.

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 ('Find Pushbuild data APIs') plus the mechanism ('by keyword'), which clearly separates discovery from the sibling actions describe_api and call_api. It stops short of explicitly naming those siblings, so the differentiation is inferred from the workflow rather than stated.

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 as a discovery/search step and the example queries show what kind of keyword input is expected. However, it never states when to use this versus describe_api or call_api, nor any exclusions or prerequisites beyond 'no key needed'.

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