Skip to main content
Glama
Sign In

ticker-scout

by ai.tickerscout
OverviewDiscussionsAdmin

Company profile and coverage manifest

get_company
Read-onlyIdempotent

Company identity and coverage manifest: name, CIK, exchange, state of incorporation, SIC industry, the fiscal period of the latest data, the SEC filings that record is built from (the annual report and the latest quarterly report, each with its own fiscal year, filing date, accession number and EDGAR link), every published record with its permanent URLs, and the predicted next filing date and form (a prediction from filing history; a filing date is not an earnings date). Pass record for an earlier record's manifest.

Input Schema

NameRequiredDescriptionDefault
recordNoAn earlier published record, by tag ('FY27Q1') or by the period its filing reports ('Q1 FY2027'). Omit for the latest. list_periods lists every record.
tickerYesTicker symbol, case-insensitive. Examples: NVDA, brk-b, BRK.B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / record
      Added value: +{
+  "description": "An earlier published record, by tag ('FY27Q1') or by the period its filing reports ('Q1 FY2027'). Omit for the latest. list_periods lists every record.",
+  "type": "string"
+}
    • changedInput schema / properties / ticker / description
      Previous value: -"Ticker symbol, case-insensitive. Examples: NVDA, brk-b."New value: +"Ticker symbol, case-insensitive. Examples: NVDA, brk-b, BRK.B."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value beyond them by disclosing the prediction caveat ('a prediction from filing history; a filing date is not an earnings date'), preventing a foreseeable misuse of the returned next-filing field.

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?

One dense, front-loaded sentence that leads with identity then coverage contents, followed by a short parameter note. The enumerated field list is long but earns its place given there is no output schema; slightly run-on but no filler.

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 carries the full burden of describing return values and does so thoroughly, covering identity fields, source filings with their metadata, per-record URLs, and the prediction field. It also covers the optional `record` selector, leaving nothing an agent needs in order to call it correctly.

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%, with the `record` parameter already documented including accepted formats ('FY27Q1' or 'Q1 FY2027') and the pointer to list_periods, so the baseline is 3. The description's single sentence ('Pass `record` for an earlier record's manifest') restates rather than extends 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 ('Company identity and coverage manifest') and enumerates the concrete data returned: name, CIK, exchange, incorporation state, SIC, fiscal period, source filings, published records, and predicted next filing. An agent knows exactly what this tool yields, though it never names the sibling it must be chosen over (e.g. get_company_metrics or list_companies).

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?

The only routing guidance is 'Pass `record` for an earlier record's manifest,' which is a parameter hint rather than a usage rule. There is no explicit statement of when to pick this over get_company_metrics, get_filings, or list_periods, so the agent must infer selection from the field list.

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

All ticker-scout toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources