Skip to main content
Glama
screener-mcp
by LogeshR15

compare_companies

Read-only

Compare 2 to 6 companies side by side on price, market cap, P/E, book value, ROCE, ROE, debt-to-equity, dividend yield, and 52-week range, with per-company red-flag checks.

Instructions

Side-by-side comparison of 2 to 6 companies: price, market cap, P/E, book value, ROCE, ROE, debt-to-equity, dividend yield, 52-week range, plus point-in-time red-flag checks per company.

Hosts that support MCP Apps (e.g. Claude Desktop) also render an interactive dashboard with the best value in each row highlighted; every host gets the same data as JSON in data.companies.

symbols: list (["ITC", "HINDUNILVR", "NESTLEIND"]) or comma-separated string ("TCS,INFY,WIPRO"). Company names and near-miss symbols are resolved like everywhere else. financial_type: "consolidated" or "standalone"

Examples: compare_companies(["ITC", "HINDUNILVR"]) compare_companies("TCS,INFY,WIPRO,HCLTECH")

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
symbolsYes
financial_typeNoconsolidated

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely new behavior: point-in-time red-flag checks per company, host-dependent dashboard rendering, and the guarantee that all hosts receive the same payload as JSON in data.companies. That host-variance disclosure is exactly the kind of context annotations cannot carry.

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?

Front-loaded with a one-line statement of the operation and its scope, followed by host behavior, then compact parameter notes and examples. Every sentence adds actionable information and format details are easy to scan.

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 an output schema present, the description needn't document return values, and it still points to data.companies. Inputs and the 2-6 bound are covered. It doesn't say whether the default financial_type is consolidated or what happens beyond the six-company cap, which keeps it at a 4.

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 0%, so the description must carry the load, and it does: symbols accepts either a JSON array or a comma-separated string, company names and near-miss symbols are resolved, and financial_type takes 'consolidated' or 'standalone'. It omits what the default is and any limit behavior when more than six are supplied, leaving a small gap.

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?

Names a specific verb and resource (side-by-side comparison of 2-6 companies) and enumerates the exact metrics returned, so the agent knows precisely what it gets. It does not name or differentiate itself from the plausible sibling get_peer_comparison, so it stops short of a 5.

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?

The 2-to-6 company constraint, the two accepted symbol formats, name/near-miss resolution, and two concrete examples give clear context for how to invoke it. There is no explicit when-not guidance or alternative named, so a 4 rather than a 5.

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