Skip to main content
Glama

List branches

list_branches
Read-onlyIdempotent

Lists every branch on an Armature hub with its latest commit ID, author, and message, newest first, so you can inspect branches and pass a branch name or commit ID to other tools.

Instructions

Every branch on the hub with its latest commit: the commit id, its author and its message, newest work first. main is the shared, agreed design; other branches are review rounds, people's workspaces or proposals. Pass a branch name or a commit id to the other tools to read there.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds what annotations cannot: the deterministic ordering (newest first) and the semantic meaning of branch types, which shapes how an agent interprets results. It does not cover pagination or volume limits for a potentially long branch list.

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?

Three short sentences, front-loaded with the returned resource and its fields, then domain semantics, then the next step. Every sentence carries information, though the branch-taxonomy sentence is the least essential of the three and could be tightened.

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?

With no parameters and no output schema, the description carries the full burden of describing return values, and it does so explicitly (commit id, author, message, newest-first). It also closes the loop on how the results are used, leaving nothing an agent needs in order to call it correctly.

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?

Zero parameters, so the baseline is 4. The description still adds navigational value by explaining that branch names and commit ids obtained here are the handles passed to other tools, which the empty schema cannot convey.

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?

States a precise verb and resource ('Every branch on the hub') plus the returned payload (commit id, author, message) and ordering (newest work first). It also explains what a branch means in this domain (main = agreed design, others = review rounds/workspaces/proposals), which distinguishes this tool from record-level siblings like get_record or branch_changes.

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?

Clearly implies this is the discovery entry point, and explicitly tells the agent the follow-up move: pass a branch name or commit id to the other tools to read there. It stops short of naming a specific alternative or stating when not to use it (e.g. how to inspect a single branch's contents directly), so it is clear context without exclusions.

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