Skip to main content
Glama

FinanceQuery

Symbol Reference Details

get_symbol_details
Read-onlyIdempotent

Get reference detail for one symbol (name, exchange, SIC code, employees, list date).

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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, so the safety profile is fully covered. The description adds only that the tool operates on a single symbol and what attributes come back; it says nothing about behavior for invalid/unknown tickers, rate limits, or data currency.

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 with no filler; the parenthetical enumeration packs real information into minimal space. Nothing is wasted, though there is no structure beyond that one line.

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 two-parameter read-only lookup with no output schema, the description enumerates the returned attributes, which compensates for the missing output schema and covers the essentials. Remaining gaps (error behavior, whether values are static or refreshed) are minor for a tool this simple.

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 'symbol' (ticker) and 'fields' (comma-separated GraphQL field names, omitted = all) are already documented. The parenthetical field list loosely corresponds to what 'fields' can select, adding mild value, but the description gives no examples of field-name syntax or default behavior 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 (get reference detail for one symbol) and enumerates the actual data returned: name, exchange, SIC code, employees, list date. An agent can tell this is a per-symbol static reference lookup, though the description does not distinguish it from adjacent siblings such as get_company_profile or get_etf_profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'one symbol' signals the single-ticker lookup path, and the field list suggests it is for identification/metadata rather than analytics. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer routing from sibling names alone.

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.