agentwebmap

Verification instructions

verification_instructions

Read-onlyIdempotent

Describe optional ownership management and its four proof methods. Call begin_ownership_claim to obtain a fresh expiring proof and a private claim secret. No ownership claim is needed for discovery.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	A domain name such as example.com (no scheme, no path).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "domain": {
-        "type": "string"
-      },
-      "methods": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "description": {
-              "type": "string"
-            },
-            "method": {
-              "enum": [
-                "llms_txt",
-                "dns",
-                "meta",
-                "well_known"
-              ],
-              "type": "string"
-            },
-            "snippet": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "method",
-            "description",
-            "snippet"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "token": {
-        "type": "string"
-      },
-      "verify_endpoint": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "domain",
-      "token",
-      "verify_endpoint",
-      "methods"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": true,
-    "properties": {
-      "detail": {
-        "type": "string"
-      },
-      "domain": {
-        "type": "string"
-      },
-      "error": {
-        "type": "string"
-      },
-      "hint": {
-        "type": "string"
-      },
-      "retry_after_seconds": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "claim_endpoint": {
+        "type": "string"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "hint": {
+        "type": "string"
+      },
+      "manage": {
+        "type": "string"
+      },
+      "methods": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "description": {
+              "type": "string"
+            },
+            "method": {
+              "enum": [
+                "llms_txt",
+                "dns",
+                "meta",
+                "well_known"
+              ],
+              "type": "string"
+            },
+            "snippet": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "method",
+            "description"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "note": {
+        "type": "string"
+      },
+      "token": {
+        "type": "string"
+      },
+      "verify_endpoint": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "domain",
+      "verify_endpoint",
+      "methods"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "detail": {
+        "type": "string"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "error": {
+        "type": "string"
+      },
+      "hint": {
+        "type": "string"
+      },
+      "retry_after_seconds": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / domain / maxLength
```
Added value: +253
```
addedInput schema / properties / domain / minLength
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "domain": {
+          "type": "string"
+        },
+        "methods": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "description": {
+                "type": "string"
+              },
+              "method": {
+                "enum": [
+                  "llms_txt",
+                  "dns",
+                  "meta",
+                  "well_known"
+                ],
+                "type": "string"
+              },
+              "snippet": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "method",
+              "description",
+              "snippet"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "token": {
+          "type": "string"
+        },
+        "verify_endpoint": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "domain",
+        "token",
+        "verify_endpoint",
+        "methods"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": true,
+      "properties": {
+        "detail": {
+          "type": "string"
+        },
+        "domain": {
+          "type": "string"
+        },
+        "error": {
+          "type": "string"
+        },
+        "hint": {
+          "type": "string"
+        },
+        "retry_after_seconds": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedOct 18, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description usefully adds that ownership claims are optional and that proofs expire, plus that the claim secret is private, which is genuinely behavioral context. It does not say whether the returned instructions vary by domain or whether anything is persisted.

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?

Three short sentences with no filler, front-loading what the tool provides before naming the follow-up call and the discovery exemption. Efficient, though the second sentence about begin_ownership_claim could arguably be left to that tool's own definition.

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?

An output schema exists, so return values need not be described. However, the description never explains the role of the required domain argument in an 'instructions' tool, nor does it enumerate the four proof methods it advertises, leaving a gap for correct invocation context.

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 single domain parameter is well documented in the schema (name format, no scheme/path). The description neither mentions the domain parameter nor explains how it affects the returned instructions, which is a notable omission for an instruction-content tool. Baseline 3 applies since the schema carries the load.

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?

States a specific verb+resource: it describes optional ownership management and its four proof methods, which is clearly distinct from sibling lookup/registry tools. It also names begin_ownership_claim, so an agent can route correctly. It stops short of saying precisely what form the returned instructions take, but the intent is legible.

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

Usage Guidelines4/5

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

It names the concrete alternative (begin_ownership_claim) and the trigger for using it (obtaining a fresh expiring proof and a private claim secret). It also gives an explicit when-not condition: no ownership claim is needed for discovery. No exclusions are stated beyond that, but the routing guidance is clear.

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

All agentwebmap tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.