Skip to main content
Glama

List Connected Repositories

list_repositories
Read-onlyIdempotent

List all repositories connected to Koalr with their health scores, activity levels, and basic stats. Use this to get an overview of the codebase landscape or find repository IDs for filtering other tools. Read-only.

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
limitNoMaximum number of repositories to return (default: 50, max: 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the trailing "Read-only." sentence is redundant. What the description does add beyond structured data is the shape of the result set (health scores, activity levels, stats), which matters since there is no output schema; it says nothing about pagination or truncation behavior despite a default limit of 50.

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 purpose followed by usage. The closing "Read-only." fragment duplicates the annotations and is the only sentence that does not earn its place.

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?

A one-parameter read-only list tool with no output schema needs little, and the description supplies both purpose and a preview of returned fields. Missing only result-ordering and truncation behavior for a 50-default list, which is a minor gap at this complexity.

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 parameter (limit) is 100% documented in the schema with default and max values, so the schema carries the full burden. The description contributes no additional semantics about ordering, filtering, or what happens when more repositories exist than the limit.

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?

States a specific verb and resource ("List all repositories connected to Koalr") and even previews the payload: health scores, activity levels, basic stats. The "list all" scope implicitly contrasts with the single-entity sibling get_repository, but that sibling is never named, so differentiation relies on inference.

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 two concrete use cases: getting a codebase overview and harvesting repository IDs to filter other tools. It does not state when NOT to use it, e.g. that get_repository should be used when a single repo's detail is needed, so an agent must infer the boundary.

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