Skip to main content
Glama

Valeur Intrinsèque

compare_stocks

Side-by-side published Score VI for 2 to 8 tickers: score, price, P/E and name. Reads the public cache and does not list the ten criteria. Counts toward the monthly Score VI quota.

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_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesTickers or company names to compare (2-8, e.g. ["AAPL","LVMH","MSFT"])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does reasonably well: it discloses the data source ('public cache', implying no auth and possible staleness), the output scope (no ten criteria), and the cost ('counts toward the monthly Score VI quota'), which is a real operational constraint. It omits failure behavior for invalid tickers and whether any caching latency applies.

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?

Three short sentences, each carrying a distinct fact: what it returns, what it does not return, and what it costs. The scope and returned fields are front-loaded with no filler.

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?

There is no output schema, so listing the four returned fields is necessary and done; the quota note covers the main operational gotcha. What is missing is edge-case behavior for unknown or mixed ticker inputs, which matters for a batch symbol tool.

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% and the schema already documents the 2-8 range with an example, so the description's '2 to 8 tickers' restates rather than adds meaning. No extra guidance on accepted formats (symbol vs company name, exchange suffixes) is given beyond 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?

The description gives a specific verb and resource ('side-by-side published Score VI for 2 to 8 tickers') and enumerates the returned fields (score, price, P/E, name). It implicitly contrasts with the deeper analysis that 'lists the ten criteria', but never names a sibling tool, so differentiation is only partial.

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 line 'does not list the ten criteria' softly tells the agent to look elsewhere when criteria-level detail is needed, and the 2-8 ticker bound implies bulk comparison rather than single-stock analysis. There is no explicit when-to-use callout, no named alternative among the many *_score / get_valuation_metrics siblings, and no stated prerequisites.

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