Skip to main content
Glama
Sign In

agentwebmap

by com.agentwebmap
OverviewDiscussionsAdmin

Directory stats

directory_stats
Read-onlyIdempotent

Directory-wide counts for Agent Web Map: domains tracked, valid llms.txt files, listed, verified, pending.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "domains_tracked": {
-        "type": "integer"
-      },
-      "last_checked": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "listed": {
-        "type": "integer"
-      },
-      "pending": {
-        "type": "integer"
-      },
-      "valid_llms_txt": {
-        "type": "integer"
-      },
-      "verified": {
-        "type": "integer"
-      },
-      "with_llms_full_txt": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "domains_tracked",
-      "valid_llms_txt",
-      "listed",
-      "verified",
-      "with_llms_full_txt",
-      "pending",
-      "last_checked"
-    ],
-    "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": {
+      "domains_tracked": {
+        "type": "integer"
+      },
+      "last_checked": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "listed": {
+        "type": "integer"
+      },
+      "pending": {
+        "type": "integer"
+      },
+      "statistics_stale": {
+        "type": "boolean"
+      },
+      "statistics_updated_at": {
+        "type": "string"
+      },
+      "valid_llms_txt": {
+        "type": "integer"
+      },
+      "verified": {
+        "type": "integer"
+      },
+      "with_llms_full_txt": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "domains_tracked",
+      "valid_llms_txt",
+      "listed",
+      "verified",
+      "with_llms_full_txt",
+      "pending",
+      "last_checked"
+    ],
+    "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"
+  }
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "domains_tracked": {
+          "type": "integer"
+        },
+        "last_checked": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "listed": {
+          "type": "integer"
+        },
+        "pending": {
+          "type": "integer"
+        },
+        "valid_llms_txt": {
+          "type": "integer"
+        },
+        "verified": {
+          "type": "integer"
+        },
+        "with_llms_full_txt": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "domains_tracked",
+        "valid_llms_txt",
+        "listed",
+        "verified",
+        "with_llms_full_txt",
+        "pending",
+        "last_checked"
+      ],
+      "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"
+}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is fully covered. The description adds only the enumeration of counted metrics — no pagination, freshness/caching, or scope caveats. Adequate but not substantive beyond 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 front-loaded sentence listing the counted categories with no filler. Slightly redundant with the title but each word contributes to telling the agent what comes back.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 shape needn't be described, and with zero params the input side is trivially complete. The only gap is failing to contrast with site_stats, which would make selection unambiguous.

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?

Zero parameters, so schema carries no semantic burden and the description has nothing to mis-specify. Baseline 4 applies; there are no argument formats to clarify.

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 ('Directory-wide counts') and enumerates exactly which metrics are returned (domains tracked, valid llms.txt files, listed, verified, pending). The 'directory-wide' qualifier implicitly separates it from site_stats, but the differentiation is not explicit.

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 only implied by the word 'counts' — an agent can infer this is for an overview/count retrieval. No explicit when-to-use statement and no mention of the sibling site_stats, which is the most likely confusion point for per-site vs directory-wide stats.

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

All agentwebmap toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources