Skip to main content
Glama

TradingAIHub directory

Search finance AI tools

search_tools
Read-onlyIdempotent

Search the TradingAIHub directory of AI tools for finance and trading (MCP servers, agent skills, APIs) by keywords, e.g. "stock prices", "crypto exchange", "options". Tools matching all words rank first. Returns the best matches with slug, links, pricing and weekly verification status.

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_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-25, default 10).
queryYesKeywords to search for.
categoryNoOptional category slug (see list_categories), e.g. market-data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so safety adds nothing. The description does contribute two real facts beyond annotations: that all-words matches are ranked first, and that results carry slug, links, pricing and weekly verification status. It stops short of covering empty-result or pagination behavior, so a 4 seems slightly generous but the ranking rule is genuine added value.

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 what is searched, then how matching/ranking works, then what comes back. No redundant restatement of the name or title.

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 simple read-only search with three fully documented parameters and no output schema, the description covers scope, ranking semantics and return fields — enough to invoke it correctly. Only edge behavior (zero results, how limit interacts with ranking) is left implicit, which is minor here.

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 baseline would be 3. The description goes beyond the bare 'Keywords to search for' schema text by specifying multi-word AND matching and ranking priority, which tells the agent how to compose a query. It adds nothing about limit or category beyond 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 — search the TradingAIHub directory of finance/trading AI tools — and enumerates the artifact types covered (MCP servers, agent skills, APIs) plus example queries. It does not explicitly contrast itself with get_tool (lookup by slug), though the schema does point at list_categories.

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?

The example keywords ("stock prices", "crypto exchange", "options") make the intended keyword-discovery use case clear, and the schema defers category browsing to list_categories. No explicit when-not or statement about using get_tool once a slug is known.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.