Skip to main content
Glama

well_known

Fetches standard /.well-known documents and summarizes OIDC, JWKS, security.txt, and app links for a domain, helping assess public configuration during reconnaissance.

Instructions

Fetch standard /.well-known documents and summarize OIDC, JWKS, security.txt and app links.

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

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It doesn't say that this performs live network requests against a third party, how many endpoints are tried, what happens when documents are missing or malformed, whether failures are partial, or anything about rate limits or auth.

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?

One front-loaded sentence that states the action and the payload with no filler. The trailing list of document types is slightly enumerative but each item earns its place by telling the agent what the summary contains.

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 moderately complex network-fetch tool with one undocumented parameter, no annotations and no output schema, the description covers what is fetched but not the shape of the summary or failure behavior. It is adequate to select the tool but thin for invoking it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter, 'domain', with 0% schema description coverage, so the description must compensate and does not. It never clarifies whether 'domain' is a bare hostname or accepts a URL/scheme/port, nor how subdomains or paths are handled.

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 pairs a specific verb ("Fetch") with a specific resource ("standard /.well-known documents") and names the document types it covers (OIDC, JWKS, security.txt, app links). An agent knows exactly what the tool returns without opening the schema, though it doesn't distinguish itself from siblings like api_discovery or dns_lookup.

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?

The mention of OIDC, JWKS, security.txt and app links implies when the tool is useful (discovery of well-known metadata for a domain), but there is no explicit when-to-use/when-not-to-use guidance and no named alternative such as api_discovery or dns_lookup for adjacent discovery tasks.

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