Skip to main content
Glama
Sign In
@chartobserver/mcp-server

@chartobserver/mcp-server

by bbusche
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get current price

get_price
Read-only

Retrieve the delayed price of any supported crypto token. Input a symbol, pair, or name; quote defaults to USD. Use for paper trading only.

Instructions

Fetch the latest price for a supported crypto token. Accepts a bare symbol (SOL), a full pair (SOLUSD, SOL-USD, SOL/USD), or a name (Solana); the quote currency defaults to USD. Prices are delayed up to 15 minutes and are for paper trading only — never for real-money decisions. Use list_supported_tokens to see valid identifiers.

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": {
      "token": "<token>"
    },
    "name": "get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesToken to price: symbol (SOL), pair (SOLUSD / SOL-USD), or name (Solana). Quote defaults to USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description reveals critical behaviors: prices are delayed up to 15 minutes and are for paper trading only, preventing real-money misuse. No contradiction with annotations.

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 concise sentences: purpose first, then input format, then important caveats. No filler; every sentence adds value.

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?

For a simple one-parameter tool without output schema, the description adequately covers purpose, input, and caveats. Lacks explicit mention of return format, but the output is often inferred. A small gap prevents a 5.

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 description largely repeats the schema's parameter description. It adds no new semantics beyond what the schema already provides, so baseline 3 is appropriate.

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?

Description clearly states the tool fetches the latest price for a crypto token, with specific verb 'Fetch' and resource 'price'. It also explains accepted input formats, making the purpose unambiguous and distinct from sibling tools like get_balance.

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 description advises using list_supported_tokens for valid identifiers and notes that prices are for paper trading only. While it doesn't explicitly contrast with alternatives, the context is clear and helpful for proper usage.

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