Skip to main content
Glama

Probe endpoint

probe_endpoint
Read-only

Probe a public HTTP or HTTPS endpoint - a load balancer, ingress hostname, or service URL - and report exactly what it answers: status code, response latency, response headers, a short body snippet, and for HTTPS the TLS certificate details (subject, issuer, expiry, whether it verifies). Unlike web_fetch this accepts plain http:// URLs, literal public IP addresses, and non-standard ports, and by default does NOT follow redirects, so the endpoint's own answer (a 301 to HTTPS, a 503 from the balancer) stays visible; set follow_redirects to chase up to 5 hops. Optional host_header probes a load balancer IP as if requesting a specific virtual host (also used as the TLS SNI). Use this to check whether an endpoint is up, what certificate it serves, or why users see errors - without asking the user to run curl. The probe dials from the Ankra platform, so private/internal addresses (10.x.x.x, 192.168.x.x, 169.254.x.x, *.svc.cluster.local, localhost) are blocked; use get_services / get_ingresses / get_pods for in-cluster state. Read-only.

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": {
      "url": "<url>"
    },
    "name": "probe_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe endpoint to probe: http:// or https://, hostname or literal public IP, optional port and path. e.g. 'http://203.0.113.7/healthz' or 'https://app.example.com:8443/status'.
methodNoHTTP method (default GET).
host_headerNoOptional Host header (and HTTPS SNI) override - probe a load balancer IP as if requesting a specific virtual host.
timeout_secondsNoRequest timeout in seconds (default 10).
follow_redirectsNoFollow up to 5 redirects and report the final response (default false: the endpoint's own redirect answer is reported).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries most of the behavioral burden and does so: probe traffic egresses from the Ankra platform, redirects are not followed by default (capped at 5 when enabled), and RFC1918/link-local/localhost/*.svc.cluster.local targets are refused. These are non-obvious execution traits an agent could not infer from annotations.

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?

A single dense paragraph that front-loads purpose and return values before scope limits and sibling routing. Nearly every clause carries information, though the return-value list and the host_header mention partially duplicate the schema and could be trimmed.

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?

No output schema exists, yet the description enumerates the response contents (status, latency, headers, body snippet, TLS subject/issuer/expiry/verification), which is exactly what an agent needs to interpret results. Combined with the network-scope restrictions and redirect semantics, nothing material is missing for a 5-parameter read-only probe.

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% and the schema already documents host_header as the Host/SNI override and follow_redirects as the 5-hop chase, so the description mostly restates it. It adds only light usage color (probing a load balancer IP as a virtual host), which does not meaningfully exceed the schema baseline.

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 (probe a public HTTP/HTTPS endpoint) and enumerates exactly what is returned: status code, latency, headers, body snippet, TLS certificate details. It explicitly contrasts itself with the closest sibling, web_fetch, on http:// support, literal IPs, non-standard ports, and redirect behavior, so an agent can pick between them without opening a 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 concrete when-to-use cases (check if an endpoint is up, inspect its certificate, diagnose user-facing errors) and names the alternative tool web_fetch. It also states a hard exclusion with a redirect to the right siblings: private/internal ranges are blocked, so use get_services / get_ingresses / get_pods for in-cluster state.

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.