Skip to main content
Glama

Signed endpoint check

verify_endpoint_sla

Probes an endpoint (best of up to 3 tries) and returns an EIP-712 SLAAttestation signed by the AgentSLA oracle: httpStatus, latencyMs, slaMet, eip712Signature and oracleSigner, verifiable with ethers.verifyTypedData (domain and types: GET https://agentsla.io/v1/attestations). Use it when another party must be able to verify the result; for a quick free look use check_endpoint. Requires walletAddress to hold an active 7-day pass (5 USDC): check_pass shows it, buy_pass sells it. Without a pass it returns an error result explaining how to pay; nothing is charged. A listed endpoint's result is also added to its public check history.

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

Input Schema

NameRequiredDescriptionDefault
endpointUrlYesFull http(s) URL to probe, e.g. "https://api.example.com/health".
maxLatencyMsNoLatency limit in milliseconds for slaMet.
walletAddressYesBase Mainnet wallet holding an active pass, e.g. "0x1234...abcd" (40 hex characters after 0x).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / endpointUrl / description
      Previous value: -"Full HTTP(S) URL of the endpoint to probe"New value: +"Full http(s) URL to probe, e.g. \"https://api.example.com/health\"."
    • addedInput schema / properties / endpointUrl / format
      Added value: +"uri"
    • addedInput schema / properties / maxLatencyMs / default
      Added value: +1000
    • changedInput schema / properties / maxLatencyMs / description
      Previous value: -"Latency limit in ms (default 1000)"New value: +"Latency limit in milliseconds for slaMet."
    • addedInput schema / properties / maxLatencyMs / maximum
      Added value: +30000
    • addedInput schema / properties / maxLatencyMs / minimum
      Added value: +50
    • changedInput schema / properties / maxLatencyMs / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / walletAddress / description
      Previous value: -"Base Mainnet wallet (0x...) holding an active pass"New value: +"Base Mainnet wallet holding an active pass, e.g. \"0x1234...abcd\" (40 hex characters after 0x)."
    • addedInput schema / properties / walletAddress / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: best-of-up-to-3 retries, the signature scheme and verification call (ethers.verifyTypedData with a documented domain/types URL), the active 7-day pass requirement, the no-charge error path when no pass exists, and the side effect that results land in a public check history — which is precisely why readOnlyHint is false. No contradiction with annotations; the description explains them.

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?

Front-loaded with what the tool does and returns, then the sibling alternative, then prerequisites and failure behavior — a rational order with no filler. Every sentence carries load, including the verification-URL pointer, which would otherwise cost the agent a search.

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?

With no output schema, the description compensates by listing the returned fields and how to verify them, and it covers the paid-prerequisite failure mode. For a three-parameter, network-touching tool that spends credits, nothing an agent needs before calling is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema cannot: walletAddress is not merely a 40-hex string, it must hold an active 7-day pass, and the retry behavior qualifies what endpointUrl's probe result actually represents. maxLatencyMs is left entirely to the schema, keeping it short of a 5.

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?

States a specific verb and resource ("Probes an endpoint") plus the exact return artifact (an EIP-712 SLAAttestation signed by the AgentSLA oracle) and enumerates the returned fields. It also distinguishes itself from the sibling check_endpoint by the verifiability of its output, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection rule: use this when another party must verify the result, use check_endpoint for a quick free look. It also names check_pass and buy_pass as the prerequisites path, so an agent blocked on the paywall knows exactly where to go next.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources