Skip to main content
Glama

Get Bike Document Outline

bike_get_document_outline
Read-onlyIdempotent

Retrieve the hierarchical outline of the open Bike document, including row IDs and text content. Optionally limit the depth of the returned tree.

Instructions

Retrieves the complete outline structure of the currently open Bike document.

Returns a hierarchical tree of rows with their IDs, text content, and children. Bike must be running with a document open for this tool to work.

Args:

  • max_depth (number, optional): Maximum depth of the outline tree to return. If not specified, returns the complete tree.

Returns: Human-readable indented outline with IDs:

Document Name (doc:root-id)

  • First item [row:Kx9]

    • Sub-item 1 [row:Lm2]

    • Sub-item 2 [row:Np4]

  • Second item [row:Qr7]

Examples:

  • Get full outline: bike_get_document_outline({})

  • Get only 2 levels deep: bike_get_document_outline({ max_depth: 2 })

Errors:

  • "Bike is not running" - Open Bike app first

  • "No document is open" - Open a document in Bike first

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_depthNoMaximum depth of the outline tree to return. If not specified, returns the full tree.
Behavior5/5

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

Annotations indicate read-only, idempotent, non-destructive. Description adds that it returns a hierarchical tree with IDs and text, and explains behavior when max_depth is omitted. No contradictions.

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?

Well-structured with sections, but slightly verbose with examples and error messages. Front-loaded with main purpose.

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?

Without output schema, description includes sample output format, examples, and error cases. Complete for the tool's complexity.

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 covers the parameter fully (100%), and description adds context that omitting max_depth returns the full tree, which adds value beyond schema.

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 clearly states it retrieves the outline structure of the currently open Bike document, using specific verb+resource. It distinguishes from siblings like bike_list_documents which lists documents, not outlines.

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?

Provides context that Bike must be running with a document open, and gives examples. However, it does not explicitly state when not to use this tool versus alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hildersantos/bike-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server