Skip to main content
Glama

FinanceQuery

Financial Ratios (TTM)

get_ratios_ttm
Read-onlyIdempotent

Get trailing-twelve-month financial ratios for a symbol.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds no behavioral context of its own — nothing about what ratio set is returned, freshness of TTM data, or how the optional fields parameter affects the payload.

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 zero filler or redundancy. It is arguably too lean rather than padded, so it scores well on structure but not perfectly, since the brevity comes at the cost of information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no description of what ratios are actually returned, so for a data-retrieval tool the agent cannot predict the response shape at all. Given a 2-parameter query endpoint with no output schema, the description should say more about the return payload and the fields default.

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% and both parameters (symbol, fields) are documented in the schema, so the baseline of 3 applies. The description contributes no additional meaning about the symbol format or about how the comma-separated field list interacts with the curated default.

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?

The description gives a specific verb (get) and resource (trailing-twelve-month financial ratios) scoped to a symbol, which is far better than a tautology. However, it does nothing to distinguish itself from the close sibling get_key_metrics_ttm, so an agent cannot tell from the text alone which of the two TTM endpoints yields ratios versus metrics.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use condition, and no mention of the sibling tools that cover adjacent TTM data. The only implied usage is 'pass a symbol to get ratios', which the agent could already infer from the name.

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.