Skip to main content
Glama

krusch_git_list_repos

Read-onlyIdempotent

Lists indexed repositories and their symbol statistics in the workspace, so agents can identify available codebases and gauge symbol coverage before searching or editing.

Instructions

List indexed repositories and symbol statistics in the workspace.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world scope, so the safety profile is fully covered. The description adds one genuinely non-structured fact: results are limited to *indexed* repositories and include symbol statistics. It does not say what happens if nothing is indexed or how statistics are aggregated, leaving modest gaps.

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?

A single front-loaded sentence with zero filler. Every clause (repositories, symbol statistics, workspace scope) carries information.

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?

With no parameters this is a simple tool, but there is no output schema, so the description carries the burden of explaining return values. "Symbol statistics" is vague — counts per language? per file? per symbol kind? — and the shape of a repo entry is never described, which a caller may need to paginate or to parse results.

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. There is no parameter semantics burden at all and the description correctly avoids inventing options like filters that the schema does not support.

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?

Specific verb+resource: "List indexed repositories and symbol statistics in the workspace." An agent immediately knows this is the discovery/listing entry point, distinct from siblings like krusch_git_file_symbols or krusch_git_read_tree which operate on a single repo's contents. It stops short of 5 because it never explicitly positions itself against those siblings.

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 implied — listing what's indexed is naturally a first step — but there is no explicit when-to-use, no ordering hint (e.g. 'call before file_symbols to discover repo names'), and no exclusions. The agent must infer the call context.

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