Skip to main content
Glama

Compare companies side by side

compare_companies
Read-only

Returns 2 to 12 companies side by side on the same measures: price move, market cap, revenue and growth, margins, price/sales, trend, with the date and basis of each company's fundamentals. Use it when the user asks to compare companies.

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": {
      "symbols": "<symbols>"
    },
    "name": "compare_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesTickers or company names to compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's added value is the disclosure that each company's fundamentals carry a date and basis, telling the agent results may be as-of differing periods. It doesn't mention behavior for unknown/invalid tickers or partial failures, which would be the next useful detail.

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

Conciseness5/5

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

Two sentences with zero filler: the measure list and cardinality come first, the use condition second. Every clause carries information an agent can act on.

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?

With no output schema, the description correctly compensates by enumerating the returned measures and noting the dating of fundamentals. Missing only edge-case behavior (unknown symbols, mixed-period results) for a tool that takes an arbitrary symbol list.

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 the single array parameter is documented with minItems 2 / maxItems 12 and accepted values (tickers or company names). The description only restates the "2 to 12" bound, adding no syntax or format guidance beyond the schema; baseline 3 applies.

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?

Specific verb and resource — returns 2 to 12 companies on a named list of measures (price move, market cap, revenue/growth, margins, P/S, trend) plus fundamentals date and basis. The multi-entity comparison scope cleanly separates it from the single-entity get_company and the filter-oriented screen_companies.

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?

"Use it when the user asks to compare companies" gives a clear triggering condition. It stops short of naming alternatives (e.g. use get_company for a single name, screen_companies to discover candidates), so an agent must infer the boundary.

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.