Skip to main content
Glama

sb_outline

Read-only

Returns a compressed tree outline of the open page—IDs, types, names, child counts, bands, and shared/site ownership—so agents can inspect structure without huge raw JSON.

Instructions

The open page as a compressed tree — id, type, name, child count, band, and whether a node is a shared global or a site overlay. Never the raw document: a real page is hundreds of KB of JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sb_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNo
chromeNoExpand shared chrome and overlays (default one line each)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.103.0
    • addedInput schema / properties / chrome
      Added value: +{
      +  "description": "Expand shared chrome and overlays (default one line each)",
      +  "type": "boolean"
      +}
  2. First observedv0.1.4

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already mark it as read-only, and the description adds meaningful behavioral context: it returns a compressed tree with specific fields and explicitly warns that it never returns the raw document because real pages can be hundreds of KB. It does not cover pagination, auth, or full return format, but it significantly enriches the safety and scope picture beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler. The core behavior and the key contrast with raw document output are front-loaded and easy to parse.

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?

The description gives a useful picture of the return structure and distinguishes it from raw document output, which matters because no output schema exists. However, it leaves the depth parameter unexplained and does not help an agent choose between this outline view and related sibling tools, so it is only minimally complete for a tool with two operational parameters.

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

Parameters2/5

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

Schema description coverage is only 50%: the chrome parameter is documented in the schema, but depth is undocumented there and is not mentioned in the description at all. The description adds no semantic meaning for either parameter, so an agent must infer what depth controls and how chrome affects output.

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?

The description clearly states that this tool returns the open page as a compressed tree, lists the fields exposed, and explicitly contrasts it with raw JSON document output. However, it does not name a specific sibling tool or clearly differentiate itself from tools like sb_page_open or sb_node_read.

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?

The phrase 'Never the raw document' implies this is a lightweight overview tool for structure rather than full page retrieval, which gives some usage context. But there is no explicit guidance on when to use this instead of alternatives such as sb_page_open, nor are prerequisites or exclusions stated.

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