Skip to main content
Glama

site_map

Read-only

Summarize all recorded data for a site or one page—pages, used buttons and links with CSS selectors, filled fields, API endpoints, common paths, and notes—before automating or restyling it.

Instructions

Summarise everything recorded for a site: its pages, the buttons and links the user actually uses on each (with CSS selectors), the fields they fill, the API endpoints behind it, common paths between pages, and saved notes. Pass page for one page in detail including its last outline. Read this before automating or restyling a site.

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": {
      "site": "<site>"
    },
    "name": "site_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPath from the map, e.g. "/orders/:id/edit".
siteYesHost, e.g. "erp.example.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, and the description is consistent with that, adding genuine value by disclosing the content shape disclosed by the call (selectors, endpoints, paths, notes). It does not discuss result size limits or whether recorded data can be stale, which would matter for a summarising read over accumulated history. That is a gap, but the behavioral picture is substantially richer than the annotation alone.

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?

The scoping and the primary payload enumeration are front-loaded, and the two short follow-up sentences do real work (single-page mode, usage trigger). The opening sentence is dense with a long comma-delimited list, which slightly hurts scanability, but nothing is redundant.

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?

With no output schema, the description carries the burden of explaining return values, and it does so by enumerating what is included. For a two-param read tool this is close to complete; only volume/pagination expectations and staleness of recorded data are unaddressed.

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. The description still adds meaning beyond the schema: `page` narrows to one path in detail and specifically returns "its last outline", while omitting `page` yields the whole site. That clarifies the mode switch that the schema does not express.

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?

The description names a specific verb ("Summarise") and resource ("everything recorded for a site") and then enumerates the payload: pages, buttons/links with CSS selectors, filled fields, API endpoints, common paths and saved notes. It also distinguishes the two modes (whole-site vs. single-page detail), so an agent can tell exactly what it gets without opening the schema.

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 states when to reach for this tool ("Read this before automating or restyling a site") and when to narrow scope ("Pass page for one page in detail"). No exclusion against a specific sibling is given, but the trigger condition is explicit enough to route an agent arriving before any automation task.

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