Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

by com.synthexforge.x402
OverviewDiscussionsAdmin

Get Service Health

get_service_health
Read-onlyIdempotent

Free, because an agent that cannot tell a live service from a dead one pays for nothing useful. part of the Capability Discovery surface; an object with 6 fields including network, receive_address.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusNoThe status of the operation.
networkNoThe `network` field of the response.
serviceNoThe `service` field of the response.
versionNoThe `version` field of the response.
settle_enabledNoThe `settle_enabled` field of the response.
receive_addressNoThe `receive_address` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / properties / network
      Added value: +{
+  "description": "The `network` field of the response.",
+  "type": "object"
+}
    • addedOutput schema / properties / receive_address
      Added value: +{
+  "description": "The `receive_address` field of the response.",
+  "type": "object"
+}
    • addedOutput schema / properties / service
      Added value: +{
+  "description": "The `service` field of the response.",
+  "type": "object"
+}
    • addedOutput schema / properties / settle_enabled
      Added value: +{
+  "description": "The `settle_enabled` field of the response.",
+  "type": "object"
+}
    • addedOutput schema / properties / status / description
      Added value: +"The status of the operation."
    • addedOutput schema / properties / version
      Added value: +{
+  "description": "The `version` field of the response.",
+  "type": "object"
+}
  2. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds some useful context by noting the tool is free and part of the Capability Discovery surface, but it does not explain health semantics, failure behavior, or how live/dead status is represented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but poorly front-loaded: it opens with a rhetorical cost justification rather than stating what the tool does. The second sentence is a fragment, and details about field count and output fields are largely redundant with the output schema.

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

Completeness3/5

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

For a simple, no-parameter health-check tool with rich annotations and an output schema, the description is minimally adequate. However, it should more directly state that it returns service health and clarify when an agent should call it, rather than emphasizing cost and output field hints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is no parameter semantics burden. The schema is empty and fully covered, making the baseline score of 4 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The description hints at health by contrasting a live service with a dead one, but never explicitly states that the tool returns service health status. It also does not distinguish this tool from nearby siblings such as verify_mcp_uptime or verify_status_body. The core purpose is inferable but not clearly specified.

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 explicit guidance on when to use this tool, when not to use it, or which sibling tool to use instead. The phrase about being 'free' does not explain the selection context or prerequisites.

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

All Synthex Forge — x402 Paid Agent Services 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