Skip to main content
Glama

Coline

List repositories

list_repositories
Read-onlyIdempotent

Lists the workspace's code repositories on Upstream that the person can open.

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": {
      "workspace": "<workspace>"
    },
    "name": "list_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNonextCursor from the previous page.
searchNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
nextCursorYes
repositoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuine context beyond that by stating results are limited to repositories the person can open. It says nothing about pagination behavior (default limit 30, max 100) or ordering, which matters for a list tool.

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. It is efficient, though its brevity is part of why usage and parameter detail are missing.

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?

For a small list tool with a required workspace param and a declared output schema, the definition supplies the key semantic facts: what is listed and whose visibility governs the results. The remaining gaps (pagination and search semantics) are minor given the schema's cursor description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: cursor and workspace are documented in the schema, but limit and search are not. The description adds no meaning for any parameter — notably it never explains what `search` matches against (name, description, owner) or how limit interacts with cursor paging.

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 (Lists) and resource (code repositories) plus the scope (the workspace's, on Upstream). The resource name itself distinguishes it from the many list_* siblings for boards, drives, calendars, etc., though it never explicitly contrasts with a sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no hint about when to page with cursor or when to use search instead of listing. The clause 'that the person can open' implies access-scoped results but does not describe an alternative tool or a condition for choosing one.

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