Skip to main content
Glama
Sign In
grid402-mcp

grid402-mcp

by oliveiratc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

grid402_crypto

Retrieves real-time spot market prices for BTC, ETH, SOL, USDC, and BASE in USD and BRL, with optional Base Mainnet payment transaction hash verification.

Instructions

Consulta preços de mercado spot em tempo real de BTC, ETH, SOL, USDC e BASE em USD e BRL.

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

Input Schema

NameRequiredDescriptionDefault
payment_tx_hashNoHash opcional de transação na Base Mainnet com 0.0005 USDC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Em tempo real' usefully signals freshness (not a cached or historical feed) and the asset list bounds coverage, but it says nothing about rate limits, error behavior, or the 0.0005 USDC payment flow that the schema parameter alludes to.

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?

One front-loaded sentence that names the verb, resource, assets and currencies with no filler. It is efficient but thin: the same single sentence has to carry all contextual weight, which it does not fully do.

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

Completeness3/5

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

For a zero-required-parameter read tool with full schema coverage and no output schema, the description is adequate to identify the data returned. It is not complete regarding the payment mechanism, which is the most consequential unknown for invoking this tool correctly.

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 description coverage is 100% and the single parameter is already documented in the schema as an optional Base Mainnet transaction hash with 0.0005 USDC. The description adds no meaning about when that parameter is needed or what happens if it is omitted, so it sits at the high-coverage baseline.

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 verb ('Consulta') and resource ('preços de mercado spot em tempo real') and enumerates the exact assets (BTC, ETH, SOL, USDC, BASE) and quote currencies (USD, BRL), so an agent knows precisely what data comes back. It never distinguishes itself from the closest sibling, grid402_forex, leaving the crypto-vs-fiat boundary to inference.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use, and no reference to any sibling tool, even though grid402_forex plausibly overlaps on currency pricing. Critically, nothing explains the payment gating implied by payment_tx_hash, so an agent cannot tell whether a call is free or requires a Base Mainnet transaction.

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