Skip to main content
Glama

MeshArc

by dev.mesharc
OverviewDiscussionsAdmin

Map a site's declared URLs

map_site

List the URLs a site declares in its sitemaps (found through robots.txt and the well-known paths, each index file walked to its children) without fetching any page. Use it first, to see how big a site is and what sections it has, before crawl_site or create_project. It cannot read content (scrape_urls and crawl_site do), and it misses pages a site links to but does not declare. Inputs: any page of the site works as url, since discovery starts at the root. search='/blog/' keeps the blog's URLs; it is a plain case-insensitive substring, not a glob, applied before limit. Cost: 1 credit per sitemap file read (usually 1 in total), never per URL. Needs write access; a read-only connection is refused with code 'read_only'.

Input Schema

NameRequiredDescriptionDefault
urlYesAny URL on the site, usually its home page.
limitNoThe most URLs to return, 1 to 5,000 (default 1,000); totals count them all.
searchNoKeep only URLs containing this text; omit for all.

Output Schema

NameRequiredDescriptionDefault
urlNoThe site that was mapped.
codeNoOnly on a failure: a machine-readable reason, e.g. read_only, validation, plan_limit or not_found.
urlsNoThe declared URLs, at most `limit`, filtered by `search`.
errorNoOnly when the call failed: what went wrong, in words an assistant can act on.
detailNoOnly on a failure: the API's own wording, when the error was rephrased.
methodNoHow the sitemaps were found, e.g. through robots.txt.
statusNoOnly on a failure: the HTTP status code.
totalsNoCounts over every declared URL and sitemap file, whatever `limit` returned.
sectionsNoThe section names the sitemaps group URLs under, e.g. 'blog'; empty when there are none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"The most URLs to return, 1 to 5,000 (default 1,000); totals still count them all."New value: +"The most URLs to return, 1 to 5,000 (default 1,000); totals count them all."
    • changedInput schema / properties / search / description
      Previous value: -"Keep only URLs containing this text, e.g. '/blog/'; omit for all."New value: +"Keep only URLs containing this text; omit for all."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The URLs a site's sitemaps declare.",
+  "properties": {
+    "code": {
+      "description": "Only on a failure: a machine-readable reason, e.g. read_only, validation, plan_limit or not_found.",
+      "title": "Code"
+    },
+    "detail": {
+      "description": "Only on a failure: the API's own wording, when the error was rephrased.",
+      "title": "Detail"
+    },
+    "error": {
+      "description": "Only when the call failed: what went wrong, in words an assistant can act on.",
+      "title": "Error"
+    },
+    "method": {
+      "description": "How the sitemaps were found, e.g. through robots.txt.",
+      "title": "Method"
+    },
+    "sections": {
+      "description": "The section names the sitemaps group URLs under, e.g. 'blog'; empty when there are none.",
+      "title": "Sections"
+    },
+    "status": {
+      "description": "Only on a failure: the HTTP status code.",
+      "title": "Status"
+    },
+    "totals": {
+      "description": "Counts over every declared URL and sitemap file, whatever `limit` returned.",
+      "title": "Totals"
+    },
+    "url": {
+      "description": "The site that was mapped.",
+      "title": "Url"
+    },
+    "urls": {
+      "description": "The declared URLs, at most `limit`, filtered by `search`.",
+      "title": "Urls"
+    }
+  },
+  "title": "MapOut",
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"The most URLs to return, 1 to 5,000 (default 1,000); totals still count them all."
    • addedInput schema / properties / search / description
      Added value: +"Keep only URLs containing this text, e.g. '/blog/'; omit for all."
    • addedInput schema / properties / url / description
      Added value: +"Any URL on the site, usually its home page."
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare write-required (readOnlyHint=false) and open-world, but the description adds the concrete consequence: 'Needs write access; a read-only connection is refused with code read_only', plus the cost model (1 credit per sitemap file, never per URL) and the no-page-fetch guarantee. That is material context beyond the structured fields and consistent with them.

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?

Front-loaded with the core action, then usage, limitations, parameter notes and cost in a tight sequence with no filler. It is dense and multi-clause, but every sentence carries information an agent needs; only the parenthetical discovery detail is slightly heavier than necessary.

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

Completeness5/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 no prose; the description covers purpose, ordering against siblings, input caveats, cost and the auth requirement. Nothing material for correct invocation is missing.

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

Parameters5/5

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

Schema coverage is 100% (baseline 3), yet the description adds real semantics: 'any page of the site works as url, since discovery starts at the root' clarifies the url parameter beyond the schema, and 'search is a plain case-insensitive substring, not a glob, applied before limit' disambiguates matching semantics and ordering versus the schema text.

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?

States a specific verb and resource (list the URLs a site declares in its sitemaps) and explains the discovery mechanism (robots.txt, well-known paths, index files walked to children). It explicitly distinguishes itself from crawl_site, scrape_urls and create_project, so an agent can pick it without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives explicit sequencing ('use it first ... before crawl_site or create_project') plus when-not guidance ('cannot read content, scrape_urls and crawl_site do') and a known blind spot ('misses pages a site links to but does not declare'). Alternatives and selection criteria are both named.

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

All MeshArc toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources