Skip to main content
Glama

PolySignals.net

Every coin right now

get_overview
Read-only

Every tracked coin in one table: spot price, the overall Buy/Sell/Hold call with score and confidence, the 1 hour window, and the daily regime call (long or flat).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description doesn't need to restate it. The description adds value by disclosing the exact payload composition, but it says nothing about freshness or snapshot timing (the title's 'right now' is never confirmed), row count, or ordering, which matter for a market-data overview.

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?

A single dense sentence that front-loads scope ('every tracked coin in one table') before enumerating the fields delivered. No filler, no repetition of the title or name.

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 carries the burden of describing the return shape, and it does so by listing the concrete fields returned. Minor gaps remain — data freshness, coin count, and ordering are unstated — but for a zero-param read-only snapshot tool this is close to sufficient.

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?

The tool takes zero parameters, so parameter semantics are moot; the baseline of 4 applies. Nothing in the description misleads about inputs.

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 clearly states the resource (every tracked coin) and enumerates the exact data returned: spot price, Buy/Sell/Hold call with score and confidence, 1-hour window, and daily regime call. It is not a restatement of the name, but it never names a sibling or explicitly contrasts with get_coin_signal, so differentiation is left implicit.

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?

Usage is implied by 'every tracked coin in one table' — an agent can infer this is the broad snapshot versus per-coin tools like get_coin_signal. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must reason about selection rather than being told.

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