Skip to main content
Glama

Get Market Ticker

get_ticker
Read-onlyIdempotent

Market snapshot: crypto top 5, SI stocks, and metrics, with the snapshot timestamp. For the publication's dated predictions and their grades, use get_scoreboard instead. This is a snapshot baked when the site was last built, not live prices — the as_of field gives its timestamp, and the live ribbon on the website refreshes more often. Takes no parameters. Returns the snapshot object plus as_of and note fields. Behaviour: read-only and public — no authentication or API key; every call is logged in aggregate (tool name, result count, coarse client class; no IP addresses).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context: the data is a build-time snapshot rather than live prices, the as_of field carries its timestamp, no authentication is required, and calls are logged in aggregate without IPs. That is useful, but return-shape detail is thin (no pagination, size, or freshness guarantees beyond as_of).

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?

Front-loaded with the resource and contents, then the sibling alternative, then the freshness caveat, then the logging note. Every sentence carries information, though the logging/privacy sentence is dense and could be trimmed without losing call-critical detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter read tool with an empty schema and no output schema, the description covers purpose, alternative, freshness semantics, return fields, and auth/logging behavior. Nothing an agent needs in order to call it correctly is missing.

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?

With zero parameters, the baseline is 4; the description correctly confirms 'Takes no parameters' so the agent does not hunt for inputs. There is no additional parameter meaning to convey.

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 resource and contents: a market snapshot of crypto top 5, SI stocks, and metrics with its timestamp. It also explicitly separates itself from get_scoreboard, so an agent can choose between them without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative (get_scoreboard) and the condition that selects it (dated predictions and grades). It further tells the agent when NOT to rely on this tool for current prices, pointing to the live ribbon, which is exactly the when/when-not guidance needed.

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.