Skip to main content
Glama

Check an endpoint (free)

check_endpoint
Read-only

Probes any HTTP(S) URL once, right now, from Cloudflare's edge and reports httpStatus, edgeLatencyMs and meetsSla (true when the status is 2xx/3xx within maxLatencyMs; an endpoint that answers GET with 405 is retried as a JSON-RPC POST). Use it before calling or paying an unfamiliar endpoint. Free and unsigned, up to 10 checks per month per IP (access shows what's left); a walletAddress with an active pass removes the limit. Sends one request to the target. For a result a third party can verify, use verify_endpoint_sla instead. The result includes a SHA-256 probeHash (a content hash, not a signature).

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": "check_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
endpointUrlYesFull http(s) URL to probe, e.g. "https://api.example.com/health".
maxLatencyMsNoLatency limit in milliseconds for meetsSla.
walletAddressNoOptional Base wallet holding an active 7-day pass: removes the monthly free-check limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / walletAddress
      Added value: +{
      +  "description": "Optional Base wallet holding an active 7-day pass: removes the monthly free-check limit.",
      +  "pattern": "^0x[0-9a-fA-F]{40}$",
      +  "type": "string"
      +}
  2. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / endpointUrl / description
      Previous value: -"Full HTTP(S) URL to check"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 meetsSla."
    • 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"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations: quota (10 checks/month per IP), the pass-based bypass, that exactly one request is sent, the 405-to-JSON-RPC-POST fallback, and a clarification that probeHash is a content hash rather than a signature. The only gap is it doesn't mention timeouts or what happens on connection failure, though the openWorldHint already signals outbound side effects.

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?

Front-loaded with the core action and result fields, and every clause (quota, fallback, sibling alternative, hash caveat) carries information. It is a dense run-on paragraph with five parenthetical asides, which slightly hurts scanability.

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 names the returned fields and explains the SLA verdict and hash, plus quota and auth behavior for an open-world network tool. Nothing an agent needs to invoke it correctly is missing.

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%, so the baseline is 3; the schema already documents all three parameters including the walletAddress pass semantics. The description only adds marginal meaning by defining meetsSla as 2xx/3xx-within-maxLatencyMs, which slightly clarifies maxLatencyMs but is not new parameter guidance.

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 any HTTP(S) URL once, right now, from Cloudflare's edge') and names the exact return fields (httpStatus, edgeLatencyMs, meetsSla). It also explicitly separates itself from the sibling verify_endpoint_sla, so an agent can choose 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 when-to-use rule ('Use it before calling or paying an unfamiliar endpoint') and an explicit when-to-use-the-other rule ('For a result a third party can verify, use verify_endpoint_sla instead'). It also discloses the free-tier limit and the wallet-based way to lift it.

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