Skip to main content
Glama

Find regional endpoints

find_regional_endpoints

Search certificate transparency logs for subdomains and surface regional endpoint names (e.g., -eu, -jp, -sg) that documentation may omit.

Instructions

Search certificate transparency logs for subdomains of a domain and surface ones that look regional (-eu, -jp, -sg, -cn ...). Providers often run regional endpoints that no documentation mentions.

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": {
      "domain": "<domain>"
    },
    "name": "find_regional_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax names to return (default 200).
domainYesApex domain, e.g. "openai.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 disclosure burden. It does add real value by naming the data source (certificate transparency logs) and the fact that results are a heuristic 'looks regional' match, not verified endpoints. It omits whether any DNS probing occurs, what happens when nothing matches, rate limits on CT log queries, and the shape of returned data.

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?

Two sentences, zero filler, with the core action front-loaded and the motivation placed after it. Every clause contributes either capability or rationale.

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 2-parameter, no-annotation, no-output-schema tool, the description covers what the tool does and why, but leaves gaps an agent needs: whether domain must be an apex (the schema says so, not the description), whether output is a flat name list, and whether any network probing or verification follows discovery.

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 both parameters are already documented, and the baseline would be 3. The description adds a bit beyond that by illustrating the regional-suffix heuristic that determines which names get returned, though it says nothing about the limit parameter or how the suffix list is applied.

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 gives a specific verb and resource — search certificate transparency logs for subdomains of a domain — plus a precise secondary behavior: filtering to names that look regional (-eu, -jp, -sg, -cn). It's clearly distinct from siblings like trace_endpoint or lookup_prefix, though it never names them.

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?

Usage is implied by the closing rationale ('Providers often run regional endpoints that no documentation mentions'), which tells an agent why to reach for this tool. However, there's no explicit when-not guidance, no mention of alternatives like observe_endpoints, and no stated prerequisites or caveats about domains with sparse CT coverage.

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