Skip to main content
Glama

list_repositories

List the caller's repositories. Wraps the same data the web UI's repo list shows.

For the common 'fix everything wrong on a branch' workflow, prefer fix_branch — it takes 'owner/repo' directly and you usually know that from the working directory / git remote.

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_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden: 'List' plus 'the caller's repositories' establishes a read-only, caller-scoped operation, and 'wraps the same data the web UI's repo list shows' signals result parity with the UI. It does not disclose ordering, pagination, or result-size limits, which is a real but modest gap for a zero-parameter read tool with an output 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?

Purpose is front-loaded in the first sentence and the usage steering follows immediately; both sentences earn their place. Minor slack in the vague phrase 'the same data the web UI's repo list shows,' which gestures at a payload without specifying it.

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 simple, zero-parameter read tool with an output schema documenting the return shape, the description covers purpose, scope, and alternative routing adequately. The one missing piece is any hint about result volume or pagination for accounts with many repositories.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already conveys. Baseline for a zero-parameter tool applies.

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 specific verb and resource ('List the caller's repositories') and scopes it to the caller's own repos, which an agent can act on directly. It also names the sibling it is not (fix_branch), so the tool is distinguishable without opening any schema.

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?

Gives an explicit alternative with the condition that selects it: for the 'fix everything wrong on a branch' workflow, prefer fix_branch, which takes 'owner/repo' directly. No explicit when-not guidance or other alternatives are given, but the routing advice is concrete and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources