Skip to main content
Glama
Sign In

spicytrade

by io.github.ferdousbhai
OverviewDiscussionsAdmin

read_instrument_quotes

Read-only

Price and daily move for tracked symbols, from the public snapshot refreshed about once a minute. Not a live quote and carries no bid/ask: sign in for those.

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": "read_instrument_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes

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?

Beyond readOnlyHint and openWorldHint, the description discloses data freshness ('refreshed about once a minute'), that values are stale snapshots, that bid/ask fields are absent, and that richer data requires authentication. It stops short of describing pagination, error behavior, or rate limits, but the behavioral picture is solid.

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 tight sentences, front-loaded with what the tool returns, followed by the key caveat. Every clause carries information an agent needs.

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 does name the returned values (price and daily move) and their freshness. For a one-parameter read tool this is nearly complete; only the symbol-format and batch-size details are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single symbols parameter has 0% schema description coverage — the schema only supplies a regex pattern and a 10-item cap with no prose. The description says 'tracked symbols' but never explains the accepted ticker format, the optional $ prefix, pair syntax, or the batch limit, so it does not compensate for the 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?

States a specific resource (price and daily move) and scope (tracked symbols, public snapshot). An agent can tell this is a current-price read rather than history or metrics, though it never names the sibling tools it differs from.

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?

Explicitly bounds the tool with 'Not a live quote and carries no bid/ask' and redirects to a signed-in path for those needs. The exclusion is clear, but no named alternative tool is offered, so routing is left partly to inference.

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

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