Skip to main content
Glama
TickerDB

TickerDB

Official

call_tool

Read-only

Execute a discovered endpoint by name with parameters, optionally saving all pages or appending rows to a SQLite table for later querying.

Instructions

Run an endpoint found with search_tools: its name plus a params object. store_as, append and fetch_all work as on the other data tools.

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

Input Schema

NameRequiredDescriptionDefault
nameYese.g. get_insider_trades
appendNoAdd rows to an existing store_as table instead of replacing it.
paramsNoEndpoint params.
store_asNoTable name: store rows in SQLite, return only a summary. Read with query_data.
fetch_allNoFollow every page into store_as in this one call.

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool's result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety bar is lower. The description adds that store_as, append and fetch_all behave consistently with the other data tools, which is real cross-tool context, but it says nothing about failure modes for bad endpoint names, pagination cost, or what happens when store_as is used without append. Note the mild tension: the tool can write rows into a SQLite table while annotations claim readOnlyHint.

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?

Two short sentences with zero filler; the prerequisite (search_tools) is front-loaded, and the shared-flag convention follows. Nothing redundant or out of order.

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?

An output schema exists, so return values need not be explained. However, this is a dynamic dispatcher with a free-form nested params object, and the definition does not address error behavior for unknown endpoints or invalid params, which is the main ambiguity an agent would hit.

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 schema already documents all five parameters, including store_as and fetch_all. The description adds convention-level meaning by saying these flags behave as on the other data tools, but contributes nothing about the params object contents or name format beyond the schema example.

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 concrete verb+resource ("run an endpoint") and ties it to the discovery sibling ("found with search_tools"), so an agent can distinguish execution from discovery. It stops short of naming what kind of endpoints (market/ohlcv) even though the sibling list makes that scope relevant.

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?

Explicitly establishes the search_tools -> call_tool workflow, which is the key routing decision an agent faces. It gives no exclusions (e.g. when to prefer query or get_market directly), but the context is otherwise clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.