AgentSLA

verify_endpoint_sla

Probe a live API endpoint and return a signed EIP-712 SLA attestation (Requires active 5.00 USDC Base Mainnet subscription or funded escrow job).

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": {
      "endpointUrl": "<endpointUrl>"
    },
    "name": "verify_endpoint_sla"
  }
}

Input Schema

Name	Required	Description
`endpointUrl`	Yes	Full HTTPS URL of the API endpoint to probe
`maxLatencyMs`	No	Target max latency in ms (default 2000)
`walletAddress`	No	Subscribed Base Mainnet wallet address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / walletAddress

Added value: +{
+  "description": "Subscribed Base Mainnet wallet address (0x...)",
+  "type": "string"
+}

First observedOct 25, 2026

TDQS

A3.5/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 discloses the paid-access requirement and that the result is a signed EIP-712 attestation, but it omits whether the probe is read-only, what SLA conditions are checked, rate limits, or how failures are reported.

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?

The description is a single front-loaded sentence with the prerequisite parenthetically attached. It contains no redundant or filler text.

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 tool with no output schema and no annotations, the description should explain the return artifact more fully. It names the signed EIP-712 SLA attestation but does not describe its structure or the SLA evaluation semantics, leaving meaningful gaps for an agent invoking the tool.

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%, so endpointUrl, maxLatencyMs, and walletAddress are already well documented in the schema. The description does not add further meaning or formatting guidance beyond the schema baseline.

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 uses a specific verb ("Probe") and resource ("live API endpoint") and states the returned artifact (signed EIP-712 SLA attestation). It is clear on its own, though it does not explicitly contrast with sibling tools such as discover_monitored_apis or get_usdc_escrow_contract.

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?

It gives an important prerequisite — an active USDC subscription or funded escrow job — which helps an agent know whether the call is permitted. However, it does not say when to choose this tool over alternatives or describe any exclusions beyond the payment requirement.

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

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