Skip to main content
Glama
TickerDB

TickerDB

Official

search_tools

Read-only

Discover TickerDB endpoints by keyword, returning each match’s name, purpose, and parameters so you can pick and run the right one.

Instructions

Find the other TickerDB endpoints: changes, the watchlist and what changed for it, insiders, insider trades and holdings, funds, fund holdings and holders, indexes, index members, TickerDB's trading models (list, detail, history, holdings, trades; Pro and Commercial plans, except a model's newest holdings, on every plan), status, account, and the raw search and universe routes. Returns each match's name, purpose and params (* = required). Empty query lists all. Run one with call_tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords, e.g. insider trades.

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool's result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful behavior the annotations do not: that matches return name, purpose and params with '*' marking required ones, and that trading-model coverage varies by plan except for newest holdings, which are available on every plan.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core instruction is front-loaded and the trailing sentences are tight, but the middle is one sprawling enumeration of roughly fifteen endpoint families. The parenthetical plan restrictions ('Pro and Commercial plans, except a model's newest holdings, on every plan') belong to the discoverable endpoints, not to the search tool, and cost more than they earn.

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?

With an output schema present, return shape need not be explained, yet the description still summarizes it. Combined with the empty-query rule and the call_tool handoff, the definition covers what an agent needs; only ranking or result-count behavior is left implicit.

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% with a decent example ('Words, e.g. insider trades'), so the baseline is 3. The description adds meaning beyond the schema by stating that an empty query returns the full list and by implying that matching operates over names, purposes and params rather than arbitrary text.

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 opens with a specific verb and object ('Find the other TickerDB endpoints') and immediately enumerates the searchable catalog, so an agent knows this is endpoint discovery rather than data retrieval. It is clearly distinguished from the sibling call_tool, which the description names as the executor.

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?

It gives the key operating rules: 'Empty query lists all' and 'Run one with call_tool', which establishes both the no-argument behavior and the natural next step. What is missing is an explicit exclusion, e.g. when to query data directly instead of searching for an endpoint.

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