Skip to main content
Glama

show_company

Read-onlyIdempotent

Show a public company in its own numbers, as it filed them with the SEC, on a card: where its revenue went in its last annual report (costs, expenses, tax and profit), ten years of revenue and net profit, where it stands among its peers (ranks only), and what it does, in its own words.

    It is the answer to any question about one company or its stock that asks for no test, whatever its verb: to
    look it up, analyse it or research it, its fundamentals, its financials, its SEC filings, what it does or how
    it is doing ("look up NVDA", "analyse Apple", "Tesla's fundamentals", "what do Microsoft's filings show",
    "what do you think about NVDA", "tell me about Apple", "is Microsoft a good company", "should I buy NVDA").
    It answers at once, in the chat, from the company's ticker or name alone; no other tool comes first.
    QuanterLab gives no view on a stock: begin your answer with the answer's `line` as it is, then at most one
    sentence; the card shows the rest. A company QuanterLab holds no annual filings for is said in one line.

    Args:
        company: The company's ticker (NVDA) or its name (Nvidia).

    The answer gives `line` (say it first), `card` (what the card shows) and `company`.
    

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": {
      "company": "<company>"
    },
    "name": "show_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond that: the answer arrives immediately in chat from a ticker or name alone, companies with no annual filings are reported in one line, and QuanterLab expresses no investment view. It stops short of covering data recency limits or failure modes for ambiguous or invalid names.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a long run-on sentence followed by a verbose parenthetical catalogue of example queries that partly repeats the earlier rule. The embedded Args block restates the schema, and the answer-formatting instructions ('begin your answer with the answer's `line`') are padded with redundant phrasing. Every sentence is not earning its place.

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-only tool with rich annotations and no output schema, the description covers purpose, accepted input formats, the no-filings edge case, and the keys returned (`line`, `card`, `company`). That is sufficient for correct invocation; only edge-case handling for bad or ambiguous inputs is left implicit.

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 description coverage is 0%, so the description carries the full burden, and it does: the single `company` argument accepts either a ticker (NVDA) or a name (Nvidia), with examples. It does not address case sensitivity, ambiguous names, or multi-listing companies, which keeps it from a 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?

The opening sentence names a specific verb and resource and enumerates the exact payload: revenue breakdown from the last annual report, ten years of revenue and net profit, peer ranks, and a business description. An agent can tell this is a single-company fundamentals card and not a scanner, backtest, or card-settings tool without opening the schema.

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

Usage Guidelines5/5

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

It gives an explicit selection rule ('any question about one company or its stock that asks for no test, whatever its verb'), a boundary condition ('asks for no test' implies test/backtest questions belong elsewhere), several concrete trigger phrasings, and a precedence instruction that no other tool comes first. That is unusually complete when-to-use guidance for a single-entity tool.

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