Skip to main content
Glama

ouroboros_brownfield

Manage brownfield repository registrations for PM interviews: scan your home directory for existing repos, register or query them, and set defaults to control which repos your coding agent uses.

Instructions

Manage brownfield repository registrations. Scan home directory for repos, register/query repos, or set the default brownfield context for PM interviews.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descNoOne-line description of the repository. Used with 'register'. Optional.
nameNoHuman-readable name for the repository. Used with 'register'. Defaults to directory name.
pathNoAbsolute filesystem path of the repository. Required for 'register' and 'set_default' actions.
limitNoMaximum number of rows to return for 'query' pagination. Omit for no limit.
actionNoAction to perform: 'scan' to discover repos from ~/, 'register' to add a single repo, 'query' to list all repos or get default, 'set_default' to toggle a repo's default flag (supports multiple defaults; does NOT clear others). Auto-detected from parameters when omitted.
offsetNoNumber of rows to skip for 'query' pagination. Defaults to 0.
indicesNoComma-separated repo numbers from the scan list (e.g. '6,18,19'). Used with 'set_defaults' action to replace all defaults at once.
scan_rootNoExisting directory to walk for the 'scan' action. Defaults to the current user's home directory.
is_defaultNoFor 'set_default' action: set to true to mark as default, false to unmark. Defaults to true.
default_onlyNoWhen true with 'query' action, return only the default repo instead of the full list. Defaults to false.
Behavior2/5

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

No annotations are present, so the description carries full burden. It only lists high-level actions without disclosing side effects, persistence behavior, or nuances like the fact that 'set_default' does not clear other defaults. This is a significant gap for a management tool that modifies state.

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 a single, concise sentence that front-loads the tool's purpose and lists the primary actions. Every word earns its place, and it is well-structured for quick comprehension.

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 tool with 10 parameters and multiple actions, the description covers scan, register, query, and set_default, but omits the 'set_defaults' action and provides no detail on behavior or edge cases. However, the schema covers parameters thoroughly, and there is no output schema requiring explanation. Adequate but with room for more context.

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?

The input schema covers 100% of the parameters with detailed descriptions, so the baseline is 3. The tool description adds no additional parameter semantics beyond what the schema already provides, but given full schema coverage, this is acceptable.

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 the tool manages brownfield repository registrations, listing specific operations: scanning home directory, registering/querying repos, and setting default context. This distinguishes it from sibling tools which focus on jobs, interviews, and execution, not repository management.

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 clear context for usage: scanning the home directory, registering/querying repos, and setting default context for PM interviews. It does not explicitly mention alternatives or when not to use, but the context is sufficiently clear for an agent to decide.

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/Q00/ouroboros'

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