Skip to main content
Glama

Upstream.codes

List repositories

list_repositories
Read-only

List repositories you can access, optionally filtered by a search term. Pass owner to list one namespace's repositories: all you can access in namespaces you belong to (private ones included), public ones elsewhere.

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
ownerNoNamespace that owns the repository (user or organization handle).
cursorNonextCursor from a previous page.
searchNo
perPageNoResults per page (default 30).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: visibility semantics (private repos within your namespaces, only public ones elsewhere), which an agent needs to interpret results correctly. Pagination behavior is not described, keeping it short of a 5.

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?

Two sentences, no filler, with the primary purpose front-loaded and the parameter-specific detail following. Every clause carries information.

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 read-only, four-parameter listing tool with no output schema, the description covers purpose, scope, and the one non-obvious parameter behavior. A brief note on result ordering or pagination would close the remaining gap, but nothing critical is missing.

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?

Schema coverage is 75%, with owner, cursor, and perPage already documented in the schema. The description meaningfully enriches the owner parameter by explaining the private-vs-public resolution rule, but adds nothing for search or cursor beyond the schema.

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?

The description opens with a specific verb+resource ("List repositories") and states the scope ("you can access"), which cleanly separates it from get_repository or search_code. It does not explicitly name a sibling, so differentiation is inferred rather than stated.

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?

It gives conditional usage guidance for the owner parameter (single namespace vs. all accessible namespaces), which implies when to use which call form. However, it never names an alternative tool or states when another tool would be a better fit, so guidance is implied rather than explicit.

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