Skip to main content
Glama
Sign In
pushbuild-mcp

pushbuild-mcp

Official
by pushbuild
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Run an API

call_api
Read-only

Run a chosen public-data API with parameters returned by describe_api to fetch JSON records, defaulting to 20 and allowing up to 500.

Instructions

Run one API with parameters from describe_api and return JSON records (default 20; set maxItems up to 500). Needs PUSHBUILD_API_KEY (free key with monthly free usage: https://pushbuild.com/apis/app/signup).

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": {
      "api": "<api>",
      "params": "<params>"
    },
    "name": "call_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiYesAPI id.
paramsYesInput parameters for that API, as describe_api lists them.

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, and the description adds material context beyond them: authentication requires PUSHBUILD_API_KEY, a signup URL explains how to obtain it, and return payloads are JSON records with a stated default page size. Error handling and rate-limit behavior are not covered, keeping it below a 5.

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?

Two dense sentences front-load the action, then layer record count and auth prerequisites; almost nothing is wasted. The dangling maxItems mention slightly muddies an otherwise tight structure.

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, nested-object tool with no output schema, the description covers action, data provenance, return format, page-size behavior, and the auth prerequisite including a signup link. Remaining gaps (failure modes, whether maxItems belongs inside params) are minor.

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 description coverage is 100%, so the api and params fields are already documented and the baseline is 3. The description adds the useful semantic that params follow describe_api's listing, but it also mentions "maxItems" which appears nowhere in the input schema, creating ambiguity about where that parameter belongs.

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 ("Run one API") plus the output shape and default record count, and distinguishes itself from describe_api by framing params as coming from that tool. It does not explicitly distinguish itself from search_apis, but the single-API scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the workflow ordering clearly: get parameters from describe_api, then invoke call_api with them. It also gives a practical constraint (default 20 records, raise maxItems up to 500). It does not state when to prefer search_apis instead, so it falls short of full when/when-not guidance.

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