Skip to main content
Glama

TradingAIHub directory

Get one tool

get_tool
Read-onlyIdempotent

Full details for one tool in the TradingAIHub directory by its slug (from search_tools): its TradingAIHub page (url) and vendor link (website_url; labelled when it is an affiliate link), homepage, docs, repo, remote MCP URL, pricing, license, npm/PyPI packages, GitHub stars and 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": {
      "slug": "<slug>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTool slug, e.g. alpha-vantage-mcp.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's added value is mostly a field inventory (affiliate labelling of website_url, remote MCP URL, stars, verification status), which is helpful but is really return-shape description rather than behavioral disclosure; error/not-found handling is unmentioned.

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?

A single front-loaded sentence that identifies the resource and lookup key before enumerating fields. The long comma-separated field list is dense but each item is informative, so little is wasted.

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 one-parameter read tool with no output schema, the description helpfully enumerates what is returned, including the affiliate-link caveat. The only gap is behavior on a missing or invalid slug.

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 coverage is 100% and the schema already documents the slug pattern and an example, so the baseline is 3. The description adds the provenance hint that the slug comes from search_tools, which is a useful complement but not syntax or format detail beyond the schema.

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 ('Full details for one tool in the TradingAIHub directory') plus the keying mechanism ('by its slug'), which cleanly separates it from the sibling search_tools that returns many results.

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 parenthetical '(from search_tools)' tells the agent this is a follow-up call after a search, which is real routing guidance. It stops short of explicit when-not-to-use or what happens with an unknown slug, so it doesn't reach the top tier.

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.