Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Call any Stockbit read endpoint

api_get
Read-onlyIdempotent

Retrieve Stockbit data by calling one GET endpoint from the catalog by ID, filling path placeholders and query parameters; returns the endpoint's data field.

Instructions

Calls one GET endpoint from api_catalog by its id. Path parameters fill the {placeholders}; query parameters use the names api_catalog lists (for documented endpoints, unknown names are refused). Returns Stockbit's data field. Prefer a dedicated tool when one exists.

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": {
      "endpoint_id": "<endpoint_id>"
    },
    "name": "api_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoQuery parameters; a list sends the key once per item.
endpoint_idYesThe id from api_catalog, e.g. get_broker_summary_v2.
path_paramsNoValues for the {placeholders} in the path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior: path parameters fill {placeholders}, query names must match what api_catalog lists, unknown names are refused for documented endpoints, and the response is Stockbit's data field. It does not cover transport failures or rate limits, but the added validation semantics are substantial.

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, front-loaded with the action, followed by the parameter contract, then the routing preference. Every clause carries information and nothing is repeated from the schema or annotations.

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 generic passthrough with nested free-form objects and no output schema, the description supplies the routing rule, the parameter contract and the return shape ('Stockbit's data field'). What remains thin is failure behavior beyond refused query names, but the essentials for correct invocation are present.

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 description goes further by explaining the contract for each parameter family: path_params map onto path placeholders and query keys are validated against the catalog's documented names. Array-to-repeated-key behavior is already in the schema, so nothing critical is missing.

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?

States a specific verb and resource ('Calls one GET endpoint from api_catalog by its id') and immediately distinguishes itself from the dedicated sibling tools by telling the agent to prefer those when available. An agent can tell exactly what this escape hatch does without opening the schema.

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?

'Prefer a dedicated tool when one exists' gives an explicit when-not rule, and the api_catalog reference implies the discovery step needed to obtain an endpoint_id. It stops short of spelling out the full workflow (catalog lookup -> id -> call) or when this generic path is strictly required versus merely convenient.

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