Skip to main content
Glama

Query Bike Rows

bike_query_rows
Read-onlyIdempotent

Search for rows in Bike outlines using outline path syntax. Filter by type, text, or attributes like @done.

Instructions

Search for rows using Bike's outline path syntax.

Outline paths are powerful queries for filtering rows:

  • /project → Top-level rows containing "project"

  • //task → All rows of type "task" (anywhere)

  • //@done → Rows with @done attribute

  • //heading → All heading rows

  • /a/b → "b" rows inside "a" rows

  • /a union /b → Rows matching "a" OR "b"

  • /a intersect /b → Rows matching "a" AND "b"

Args:

  • outline_path (string, required): The outline path query.

Returns: Matching rows formatted as:

  • Row text [row:XXX]

Or scalar result (count, boolean, text) depending on the query.

Examples:

  • Find all tasks: bike_query_rows({ outline_path: "//task" })

  • Find headings: bike_query_rows({ outline_path: "//heading" })

  • Find by text: bike_query_rows({ outline_path: "//project" })

  • Find with attribute: bike_query_rows({ outline_path: "//@done" })

Errors:

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outline_pathYesOutline path query (e.g., '//task', '//@done', '//heading').
Behavior5/5

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

Annotations already mark readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds important behavioral details: return format (row text or scalar), error conditions, and prerequisites. 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?

The description is well-structured with sections for syntax, args, returns, examples, and errors. It is slightly lengthy but justified by the query complexity. Front-loading the purpose and examples helps quick understanding.

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?

For a query tool with one parameter and no output schema, the description covers syntax, return format, examples, and error prerequisites comprehensively. No critical gaps remain.

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 description coverage is 100% with a basic example. The tool description greatly expands meaning by detailing outline path syntax, advanced operators (union, intersect), and multiple examples, far exceeding the schema's brief note.

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?

Title 'Query Bike Rows' and description 'Search for rows using Bike's outline path syntax' clearly state the tool's function. Examples differentiate it from siblings like bike_create_rows.

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?

The description provides explicit context with examples and error messages indicating prerequisites (Bike running, document open). It lacks direct comparison to alternatives like bike_get_document_outline but still guides usage effectively.

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