Skip to main content
Glama

get_site_outline

Read-onlyIdempotent

Site shape: every layout and shared section (sections: fragments/* by name, with page count, whether the file exists and staged-change flag), whether a layout is missing, redirects count, menus grouped by where they show, and collections with their page placements. Answers 'is my layout missing', 'which shared sections exist and where', 'where does this menu show' without listing every page. Read-only; indexing mirrors list_pages (a fresh import may still be indexing).

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite slug, e.g. acme-studio

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Why you're calling this (activity log).",
      -  "minLength": 1,
      -  "type": "string"
      -}
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / context / description
      Previous value: -"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."New value: +"Why you're calling this (activity log)."
  3. Changed3 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"One sentence: why you are calling this tool and what you are trying to accomplish. Stored on the site's activity log and visible to everyone on the site — never put secrets or personal data here."New value: +"Optional: one sentence on why you are calling this (shown in the site's activity log; no personal data)."
    • removedInput schema / properties / guestToken
      Removed value: -{
      -  "description": "Guest token from start_site. Send it on every call until claim_site. Omit when this chat is already signed in to Dotsy.",
      -  "minLength": 20,
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "context"
      -]New value: +[
      +  "site"
      +]
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only and idempotency, so the description's added value is the indexing caveat ('a fresh import may still be indexing') and the per-section metadata such as staged-change flags. That is useful behavioral context the annotations cannot express, though it says nothing about response size or pagination.

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 purpose is front-loaded in a short label followed by a dense parenthetical enumeration, then the use cases, then the caveat. Almost every phrase carries information, though the parenthetical list is heavy and slightly hard to scan in one pass.

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 does the work of describing the return shape field by field, plus the staleness caveat for freshly imported sites. It is complete enough to call correctly; only response format details like ordering or size are unspecified.

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?

There is a single required parameter, and schema coverage is 100%, so the schema already documents the site slug with an example. The description adds no further meaning about the parameter, which is acceptable given full schema coverage.

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 opens with 'Site shape' and then enumerates exactly what is returned: layouts, shared sections with page counts/existence/staged flags, missing-layout check, redirects count, menus grouped by location, and collections with page placements. It explicitly contrasts with list_pages ('without listing every page'), so an agent can distinguish it from siblings 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 names the concrete questions the tool answers ('is my layout missing', 'which shared sections exist and where', 'where does this menu show') and points to list_pages as the alternative for per-page enumeration. It lacks an explicit 'do not use this for X' exclusion, but the routing context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources