Skip to main content
Glama

Leeway Financial Data

ai_company

ai_company
Read-only

Research on one stock, passed as symbolexchange in SYMBOL.EXCHANGE form. topic is whatsnew, timeline, competitors, risks, price_drivers, industry, or sector. Wallet pay-per-use. HTTP 402 if the wallet is too low. maxAgeDays=0 forces a refresh. lang (de or en) applies to whatsnew, timeline, competitors, and risks. industry covers the company's narrow business field, such as Tobacco. sector covers the broad group, such as Consumer Defensive, and is not about the company's own industry. industry returns HTTP 400 when the company has no industry. sector returns HTTP 400 when the company has no sector. For a commodity or currency, use ai_asset.

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": {
      "topic": "<topic>",
      "symbolexchange": "<symbolexchange>"
    },
    "name": "ai_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoResponse language: de or en.
topicYesWhich company research brief.
sourcesNoPass true to include sources. Omit this parameter to leave sources out.
maxAgeDaysNoMaximum age of a cached context object in days.
symbolexchangeYesTicker in SYMBOL.EXCHANGE format, for example AAPL.US.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds substantial context the agent could not otherwise know: pay-per-use wallet billing, HTTP 402 on insufficient funds, HTTP 400 for missing industry or sector, and maxAgeDays=0 forcing a cache refresh. These failure modes and cost implications directly affect whether and how an agent should call it.

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?

Purpose is front-loaded in the first sentence, followed by topic disambiguation, then payment and error behavior, then parameter notes. It reads as a dense run-on list with repeated "HTTP 400" phrasing, but nearly every clause carries information an agent needs.

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

Completeness5/5

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

With no output schema, the description still conveys what the call yields (a research brief for a chosen topic, optionally in German or English, optionally with sources) plus cost, caching, and error behavior. For a five-parameter read tool, nothing essential to correct invocation is missing.

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 is 3, but the description adds real meaning beyond the schema: which topics lang actually affects (whatsnew, timeline, competitors, risks) and the exact refresh semantics of maxAgeDays=0. It does not explain sources or maxAgeDays bounds beyond the schema, keeping it at 4 rather than 5.

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 ("Research on one stock") and pins the identifier format to SYMBOL.EXCHANGE. It also separates the two easily-confused topics (industry = narrow business field, sector = broad group) and routes commodities/currencies to ai_asset, so an agent can tell this apart from its siblings without opening a schema.

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?

Explicitly redirects non-equity assets ("For a commodity or currency, use ai_asset") and clarifies which topic to pick when industry and sector overlap, which is the main selection ambiguity here. It does not say when to prefer this over fundamentals or news for company information, so a small gap remains.

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.

Resources