mcp.xynaptic

crypto-global

Xynaptic Crypto Global — global crypto market snapshot (CoinMarketCap Pro): total market cap, BTC/ETH dominance, 24h volume, market trend assessment. GET (no params). Usage: Use for overall crypto market context: total market cap, BTC dominance, 24h volume. Combine with crypto-movers to identify what drives the market. [price: $0.010 per call, x402/USDC]

Input Schema

Name	Required	Description	Default
`params`	Yes	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026
- addedInput schema / properties / params / required
```
Added value: +[]
```
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "params"
+]
```

Changed4 schema fields changedOct 2, 2026

removedInput schema / properties / body

Removed value: -{
-  "description": "JSON body for POST endpoints (e.g. insurance, ai-chat, production-risk)",
-  "type": "object"
-}

changedInput schema / properties / params / description

Previous value: -"query parameters, e.g. {city: 'Paris', type: 'Appartement'}"New value: +"query parameters"

addedInput schema / properties / params / properties

Added value: +{
+  "btc_dominance": {
+    "description": "example: 57.8",
+    "type": "number"
+  },
+  "total_mcap_usd_t": {
+    "description": "example: 2.88",
+    "type": "number"
+  },
+  "volume_24h_usd_b": {
+    "description": "example: 85.2",
+    "type": "number"
+  }
+}

addedInput schema / required
```
Added value: +[]
```

First observedOct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the upstream data source (CoinMarketCap Pro), the GET/no-param access pattern, and the cost/payment model ($0.010 per call, x402/USDC) — meaningful behavioral context an agent needs before invoking. It does not cover caching, rate limits, or error behavior, keeping it below 5.

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?

Front-loaded with the core purpose and return fields, then usage, then a bracketed pricing note. Slightly redundant in restating the market-cap/dominance/volume list twice, but no filler sentences.

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?

No output schema exists, and the description compensates by enumerating the returned metrics and naming the data source. With the pricing and usage context included, an agent has enough to call it correctly; only pagination/refresh semantics are absent.

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%, so baseline is 3. The description usefully clarifies 'GET (no params)', which corrects the misleading schema where the nested 'params' properties (btc_dominance, total_mcap_usd_t, volume_24h_usd_b) are actually response fields, not inputs. It adds clarification but no syntax or format detail beyond that.

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?

States a specific verb+resource ('global crypto market snapshot') and enumerates exactly what it returns: total market cap, BTC/ETH dominance, 24h volume, trend assessment. This clearly distinguishes it from siblings crypto-price (single asset) and crypto-movers (top movers).

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?

'Use for overall crypto market context' plus 'Combine with crypto-movers to identify what drives the market' gives an explicit use case and names a sibling for a complementary task. It stops short of stating an exclusion, e.g. that crypto-price should be used for a single coin, so it is clear but not fully routing.

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

All mcp.xynaptic tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?