Skip to main content
Glama
Sign In

Returnolio

by com.returnolio
OverviewDiscussionsAdmin

Compare stocks

compare_stocks
Read-only

Compare Returnolio scores and pillar breakdowns for up to 5 tickers side by side. The response includes an app link to the full comparison. Read-only.

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": {
      "tickers": "<tickers>"
    },
    "name": "compare_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYesUp to 5 ticker symbols

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the trailing 'Read-only' merely restates that. The valuable addition is disclosing that the response contains an app link to the full comparison, which tells the agent the output is a summary rather than a complete dataset; beyond that there is no mention of rate limits, error behavior on unknown tickers, or ordering of results.

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?

Two short sentences, front-loaded with the core comparison behavior and the cap. The only wasted words are the redundant 'Read-only.' tail, which duplicates the annotation.

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 comparison tool with no output schema, the description covers what is compared, the input limit, and a hint at the return payload (app link). Only minor gaps remain, such as behavior with invalid or unresolved tickers.

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 parameter already states 'Up to 5 ticker symbols', so the description's 'up to 5 tickers' adds no meaning beyond the schema. With one well-documented parameter, the baseline of 3 applies.

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 names a specific verb and resource ('Compare Returnolio scores and pillar breakdowns') plus a scope constraint ('up to 5 tickers side by side'), so the agent knows exactly what the tool produces. It only implicitly separates itself from the sibling compare_companies (stocks vs companies), so it falls short of full sibling differentiation.

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 'side by side' comparison framing implies when to use it, but there is no explicit guidance on when to prefer it over compare_companies or get_stock_score, and no stated prerequisites or exclusions. Usage is inferable rather than directed.

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

All Returnolio 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