Synmerco

get_crypto_health

Check crypto payment infrastructure status before initiating high-value transfers. Returns chain health, RPC latency, and recent settlement times so your agent picks the fastest rail. Free, no auth required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>"
    },
    "name": "get_crypto_health"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes	L2 chain to check

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

There are no annotations, so the description carries the transparency burden. It discloses that the tool is free and requires no auth, and it states what the tool returns. While it doesn't mention rate limits or failure behavior, it clearly implies a read-only status check, which is adequate for this tool's scope.

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 sentences, each earning its place: purpose, return value/usage context, and auth/free status. The description is front-loaded with the verb and resource, and there is no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read-only health check, the description covers purpose, when to use, auth/free status, and return contents. No output schema is present, but the description lists the key return fields, so the agent has enough context to invoke and interpret the result.

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% with a clear enum and description for the single 'chain' parameter. The tool description adds contextual value by explaining that the goal is picking the fastest rail, but it doesn't add details about how the chain value affects the output beyond what the schema already provides.

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 uses the specific verb 'Check' with a clear resource ('crypto payment infrastructure status') and states what is returned (chain health, RPC latency, settlement times). It also frames the tool's purpose in a decision-making context ('picks the fastest rail'), making it clearly distinct from the broader set of sibling tools.

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?

The description explicitly says to use the tool 'before initiating high-value transfers' and explains why (to pick the fastest rail). This gives clear usage context, though it doesn't name specific alternatives or excluded cases.

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

All Synmerco 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?