Skip to main content
Glama
Sign In

SYNTHORA x402 Intelligence Mesh

by com.hergertsynthora
OverviewDiscussionsAdmin

bitcoin_fees

Read-onlyIdempotent

SYNTHORA bitcoin-fees: Bitcoin fee tiers in sat/vB (fastest/half-hour/hour/economy/minimum) plus current block height. Source: mempool.space public API, keyless. Bitcoin only. [x402: 0.01 USDC per call on Base]

Input Schema

NameRequiredDescriptionDefault
redNoOptional Bitcoin-only selector; exact lowercase bitcoin. Omit for Bitcoin. Does not select fee tier.
networkNoOptional Bitcoin-only selector; exact lowercase bitcoin. Omit for Bitcoin. Does not select fee tier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / input
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / network
      Added value: +{
+  "const": "bitcoin",
+  "description": "Optional Bitcoin-only selector; exact lowercase bitcoin. Omit for Bitcoin. Does not select fee tier.",
+  "type": "string"
+}
    • addedInput schema / properties / red
      Added value: +{
+  "const": "bitcoin",
+  "description": "Optional Bitcoin-only selector; exact lowercase bitcoin. Omit for Bitcoin. Does not select fee tier.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • removedInput schema / properties / input / description
      Removed value: -"product parameters (JSON or text)"
  3. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text). Example: {\"input\": \"{}\"}"New value: +"product parameters (JSON or text)"
  4. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text)"New value: +"product parameters (JSON or text). Example: {\"input\": \"{}\"}"
  5. Added
  6. Removed
  7. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"product parameters (JSON or text). Example: {\"protocol\": \"aave\"}"New value: +"product parameters (JSON or text)"
  8. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (mempool.space public API, keyless) and the access cost (0.01 USDC per call via x402), which an agent needs to know before invoking.

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?

Dense and front-loaded: resource, return shape, source, payment model all in one compact block. The 'SYNTHORA bitcoin-fees:' prefix duplicates the tool name and the separate x402 bracket could be smoother, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing returns and does so (the five fee tiers plus block height), alongside source and cost, while annotations cover the read-only profile. Minor gaps remain around freshness/caching of the block-height value and error behavior.

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 both parameters have explicit const values, so the schema fully documents them. The description only echoes 'Bitcoin only', adding nothing about the odd duplicated red/network selectors; baseline 3 applies when the schema does the heavy lifting.

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 resource (Bitcoin fee tiers) and enumerates exactly what comes back (fastest/half-hour/hour/economy/minimum in sat/vB plus current block height), which is more specific than most siblings. However, it never names or contrasts an alternative (e.g. gas_oracle_multi), so the differentiation is implicit rather than stated.

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?

'Bitcoin only' and the fee-tier enumeration imply this is the tool for Bitcoin fee lookups, giving implied usage context. There is no explicit when-to-use/when-not guidance and no pointer to a sibling for multi-chain or non-Bitcoin fee data, so routing is left to inference.

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

All SYNTHORA x402 Intelligence Mesh toolsInspect
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