Skip to main content
Glama

Create Bike Document

bike_create_document

Create a new document in Bike, optionally populated with an outline structure of headings, tasks, and formatted rows.

Instructions

Creates a new document in Bike, optionally with an outline structure.

Args:

  • structure (array, optional): Outline structure to populate the document. Each node can have:

    • name (string): Text content (may contain HTML if html=true)

    • type (string, optional): Row type (body, heading, task, code, quote, note, unordered, ordered, hr)

    • children (array, optional): Nested child nodes If not provided, creates an empty document.

  • html (boolean, optional): If true, name fields may contain HTML formatting: , , , , ,

Returns: Document info: "Untitled (doc:XXX)"

Examples:

  • Empty doc: bike_create_document({})

  • With structure: bike_create_document({ structure: [ { name: "Project", type: "heading", children: [ { name: "Task 1", type: "task" }, { name: "Task 2", type: "task" } ]} ] })

  • With HTML: bike_create_document({ structure: [{ name: "Click <a href="https://example.com">here" }], html: true })

Errors:

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoIf true, name fields may contain HTML formatting (strong, em, code, mark, s, a).
structureNoOutline structure to populate the document. Same format as bike_create_rows.
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses the return format ('Untitled (doc:XXX)'), behavior with/without structure, and error conditions. This adds valuable context for the agent.

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?

The description is well-structured with Args, Returns, Examples, and Errors sections. It is concise yet comprehensive, front-loading the main purpose and using examples efficiently.

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?

Given the tool's complexity (2 params, nested structure, no output schema), the description covers all necessary aspects: parameter details, return value, error messages, and usage examples. This ensures the agent can use it correctly.

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?

With 100% schema coverage, baseline is 3, but the description elaborates on the nested structure of the 'structure' parameter, explains HTML formatting, and provides concrete examples, adding significant meaning beyond the 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 'Creates a new document in Bike, optionally with an outline structure.' The verb 'create' and resource 'document' are specific, and it distinguishes from sibling tools like bike_list_documents or bike_get_document_outline.

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 provides clear context for when to use (creating documents), includes error messages like 'Bike is not running' for diagnostics, and gives examples. However, it doesn't explicitly state when not to use or mention alternative tools.

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