Agent Bobby Free

Compare two stocks for free

compare_two_stocks_free

Read-onlyIdempotent

Use this when the user names exactly two US-listed stocks or ETFs and wants a compact evidence comparison. Returns cached public price action and already-computed Bobby context. It does not choose a winner, inspect a portfolio, or execute a trade.

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

Input Schema

Name	Required	Description	Default
`tickers`	Yes	Exactly two distinct stock or ETF tickers

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding beyond them: the data is 'cached public price action' and 'already-computed Bobby context,' which signals staleness and precomputation. The undefined term 'Bobby context' loses a little clarity.

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, the usage trigger front-loaded, then return content, then exclusions. Nothing is redundant and nothing reads as 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?

With no output schema and only one parameter, the definition supplies most of what an agent needs: invocation condition, data source freshness, and explicit non-goals. The only real gap is that 'Bobby context' is left unexplained.

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 single parameter already carries a pattern, min/max items, and a description. The prose restates 'exactly two' and adds only the 'US-listed' qualifier, so it is at the baseline rather than meaningfully beyond the schema.

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?

States a specific verb and resource ('compare exactly two US-listed stocks or ETFs') plus the output character ('compact evidence comparison'), which separates it from the single-stock brief and market-pulse siblings without needing their schemas.

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 trigger is explicit: 'Use this when the user names exactly two US-listed stocks or ETFs.' Negative guidance is also given ('does not choose a winner, inspect a portfolio, or execute a trade'), though it stops short of naming what to call for a single ticker or a portfolio request.

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

All Agent Bobby Free tools Inspect

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

Need Help?