scrape_coinbase
Get a Coinbase ticker. Use for crypto-pricing agents.
Example call: {"symbol": "BTC-USD"}
Cost: $0.005–$0.05 USDC on Base per call.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
GoCreative Agent API
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. Discloses cost and provides an example call, but does not mention rate limits, idempotency, or whether it is read-only (though implied by 'get'). Adequate but not thorough.
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 plus an example call. Purpose first, then usage guidance, then cost. No unnecessary words.
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?
Given only one parameter, no output schema, and no annotations, the description covers the essential information: purpose, example, and cost. Missing return format details but sufficient for a simple ticker tool.
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 0%, so description must compensate. Provides an example value 'BTC-USD' which hints at format, but does not explain the parameter's meaning or allowed values explicitly.
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 verb 'Get' and resource 'Coinbase ticker', and specifies the use case for 'crypto-pricing agents'. This differentiates it from other scrape_* tools targeting different platforms.
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?
Explicitly says 'Use for crypto-pricing agents', providing clear context for when to use. Does not include when-not-to-use or alternatives, but the sibling list implies it is Coinbase-specific.
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.
TDQS
B3.2/5.0
Disambiguation2/5
The set is riddled with near-duplicates: lookup_reddit/scrape_reddit, lookup_wikipedia/scrape_wikipedia, lookup_dockerhub/scrape_dockerhub, lookup_steam/scrape_steam, enrich_googlereviews/enrich_reviews, lookup_ip/lookup_ipinfo, and multiple crypto-pricing tools (lookup_crypto, lookup_coingecko, bundle_crypto_360, scrape_binance, scrape_coinbase). Descriptions try to differentiate with phrases like 'heavier than' or 'same domain but with full thread parsing,' but the boundaries are fuzzy and an agent can easily pick the wrong one.
Naming Consistency4/5
Naming follows a fairly consistent prefix-based snake_case pattern (lookup_, scrape_, enrich_, bundle_, search_, ai_, data_) where the prefix denotes action weight and the noun identifies the target. Minor deviations exist: posts_x, ai_ask/pro/ultra (model-tier names instead of resources), sslstatus (missing underscore), and lookup_useragents_top are slightly off-pattern.
Tool Count1/5
172 tools is an extreme count, far beyond even the 50+ floor for a score of 1. This floods the agent's context and tool-selection space, making every call require a search through a massive list. While aggregation servers can justify more tools, this volume is unmanageable and every tool must be evaluated by the agent.
Completeness3/5
The surface is extraordinarily broad but unevenly deep: many sources have both a light lookup and a heavy scrape variant, while other areas have just a single shallow endpoint. There is no coherent domain with complete lifecycle coverage, and despite the huge catalog, common capabilities are still absent. The breadth prevents obvious gaps, but depth and coherence suffer.