Skip to main content
Glama

List branches

argon_branch_list
Read-onlyIdempotent

List a project's branches with their heads, checkout state, and TTLs to inspect branch status before merging or discarding changes.

Instructions

List a project's branches with their heads, checkout state and TTLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "argon_branch_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the useful detail that TTL and checkout state are surfaced, but says nothing about pagination, ordering, or behavior when the project has no branches.

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 with no filler; the resource comes first and the returned fields trail as useful detail. Slightly terse given it omits scope/limit qualifiers, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only listing with no output schema, the description adequately conveys what comes back (heads, checkout state, TTLs) and the annotations cover safety. Missing only pagination/ordering expectations and empty-result behavior.

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 single 'project' parameter is fully documented in the schema (100% coverage), so baseline is 3. The description only implies that project scopes the listing and adds no format, naming convention, or error semantics beyond that.

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?

Names a specific verb and resource ('List a project's branches') and adds what each entry carries (heads, checkout state, TTLs). No sibling in the provided list covers branches, so no direct differentiation is needed, though it never explicitly scopes itself against other read tools like argon_diff or argon_connect.

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?

Usage is only implied: the enumerated return fields suggest you call it when you need branch heads or checkout status before pinning, sandboxing, or merging. There is no explicit when-to-use, precondition, or alternative named, so an agent must infer the trigger.

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