Skip to main content
Glama
Sign In
polygon-mcp

polygon-mcp

by atomcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

crypto_get_snapshot

Get a real-time snapshot for a single cryptocurrency pair by symbol, delivering key market metrics like price and volume for immediate analysis.

Instructions

Get snapshot for a single crypto pair.

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": {
      "symbol": "<symbol>"
    },
    "name": "crypto_get_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It merely says 'Get snapshot' without explaining what the snapshot includes, data freshness, or any limitations. This is minimal and leaves the agent uncertain about the tool's output and side effects.

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?

The description is a single, front-loaded sentence with no superfluous words. It conveys the essential purpose efficiently.

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

Completeness2/5

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

The tool has no output schema and no annotations, so the description must explain what a snapshot is and what the return value looks like. It does neither, nor does it clarify the symbol format. The description is too sparse for a standalone tool.

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 schema has one required parameter 'symbol' with 0% description coverage. The description adds a hint that the symbol is a crypto pair, but does not specify the expected format (e.g., 'BTCUSD' vs 'BTC/USD'). This is insufficient compensation for the lack of schema documentation.

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?

The description clearly states the action (Get) and the resource (snapshot) with a specific scope ('single crypto pair'), distinguishing it from siblings like crypto_get_snapshot_all and other asset-class snapshot tools.

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 description implies usage for a single crypto pair, but does not explicitly contrast with alternatives like crypto_get_snapshot_all. The context signals list sibling tools, but the description itself provides no direct guidance on when to prefer this tool.

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

Deploy Server

Other Tools