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). [price: $0.010 per call, x402/USDC]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

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

B3.4/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. It does disclose the transport ('GET'), that no parameters are needed, the upstream source (CoinMarketCap Pro), and the x402/USDC price of $0.010 per call, which is genuinely useful pre-invocation context. It says nothing about rate limits, freshness/latency of the snapshot, or failure modes.

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?

One dense sentence plus a bracketed pricing note; the resource and metric list are front-loaded and nothing is wasted. The pricing is separated into its own bracket so it does not dilute the core purpose.

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 no-param, no-output-schema snapshot tool with no annotations, the description substitutes for a return schema by naming the four returned fields, which is the right call. What remains missing is freshness/latency of the global snapshot and any indication of response structure, but the essentials for correct invocation are present.

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 tool is explicitly parameterless, so the schema already carries the semantics. The description's 'GET (no params)' usefully confirms that the nested 'params' object with dominance/mcap/volume examples is not caller-supplied input, which is a real clarification given the confusing schema, but it adds 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific resource ('global crypto market snapshot') and enumerates the exact metrics returned: total market cap, BTC/ETH dominance, 24h volume, and a trend assessment. That is well beyond a tautology. It does not, however, distinguish itself from siblings like crypto-market, crypto-brief, or crypto-fear-greed, so it stops short of a 5.

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 statement of when to use this tool versus the many adjacent crypto tools (crypto-market, crypto-brief, crypto-fear-greed, crypto-movers). The only routing-like signal is 'GET (no params)', which says how to call it, not when. An agent must infer the use case from the metric list alone.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?