Skip to main content
Glama

AutoTasker Hub — China Social Data API

usdc_price

Current USDC/USD peg and price from CoinGecko. For arbitrage checks. $0.01 USDC.

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

Input Schema

NameRequiredDescriptionDefault
symbolNoUSDC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. It names the upstream source (CoinGecko) and claims the value is 'current', which is useful, but it says nothing about update cadence, caching, rate limits, failure behavior, or precision of the returned peg value.

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?

Three short fragments with the core purpose front-loaded and no filler. The telegraphic style ('$0.01 USDC') is slightly cryptic but does not obstruct understanding.

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 simple single-value lookup with no output schema, the description covers source and purpose adequately. It leaves unresolved the meaning of the symbol parameter and the shape of the response (raw price vs. peg deviation), which an agent would need when deciding whether to trust the result.

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?

Schema coverage is 0% for the single 'symbol' parameter, and the description does not clarify its semantics at all. It is ambiguous whether the parameter can accept other stablecoin symbols or is effectively fixed at the USDC default, which is exactly the gap the description should close.

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 states a specific resource (USDC/USD peg and current price) with a named data source (CoinGecko), which is enough for an agent to know exactly what is returned. It does not explicitly distinguish itself from sibling price tools such as btc_usd_rate, so it falls short of the top score.

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?

'For arbitrage checks' implies a usage context, giving a hint about when this is appropriate. There is no explicit when-not guidance, no mention of alternative tools for other assets, and no statement about how often to poll or whether the value is suitable for accounting vs. trading decisions.

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.