Skip to main content
Glama

readme

Fetches BowThruster quickstart, architecture guide, or unified skill template so agents can format pipe tables and operate BowThruster correctly.

Instructions

Read the BowThruster README, System Architecture Guide, or the unified 'bowthruster' SKILL.md template so you know how to format pipe tables and operate BowThruster.

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

Input Schema

NameRequiredDescriptionDefault
sectionNoWhich documentation to return: 'readme' (default inline quickstart + unified skill), 'full_readme' (full README.md), 'guide' (full architecture & brownfield guide), 'skill'/'skills' (unified bowthruster SKILL.md template), or 'all'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden and clearly implies a safe read of static documentation. It doesn't describe output shape or note that non-listed enum values (change, navigate, qa, all) are also valid, so some behavioral detail is left to the schema.

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?

A single front-loaded sentence that names the resources first and the rationale second, with no padding. Efficient, though the 'format pipe tables' rationale is slightly narrower than the tool's full scope.

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?

For a simple single-parameter read tool with no output schema, the description is broadly adequate: it explains what is returned. It stops short of explaining how the returned documentation differs across sections or noting the default behavior when section is omitted.

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?

Schema coverage is 100% and the enum fully documents the section values, so the schema does the heavy lifting. The description names three of the nine enum values but adds no extra meaning about defaults or how the sections differ beyond what the schema states.

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?

States a specific verb ('Read') with three named resources (README, System Architecture Guide, SKILL.md template), so the agent knows this retrieves documentation. It doesn't explicitly contrast with siblings like status or atlas, but the documentation-retrieval purpose is unambiguous.

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 clause 'so you know how to format pipe tables and operate BowThruster' implies when to reach for it, but there is no explicit when-not guidance and no alternative tool is named for documentation lookups.

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

Deploy Server

Other Tools