Skip to main content
Glama

List connected repositories

list_repositories
Read-only

The GitHub repositories the signed-in user has connected, which they can list for sale.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNoThe maximum number of records to return
filterNoA filter to apply to the query: either a condition {"field": ..., "operator": ..., "value": ...} or an {"and": [...]} / {"or": [...]} group of conditions and groups (nestable). Operators: contains, eq, greater_than, greater_than_or_equal, ilike, in, is_distinct_from, is_nil, is_not_distinct_from, less_than, less_than_or_equal, like, not_eq, string_ends_with, string_starts_with. For 'is_nil' the value is true or false; for 'in' the value is an array. Fields: id, github_id, full_name, private, removed_at, installation_id.
offsetNoThe number of records to skip
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as "the user" or "a buyer".
result_typeNoThe type of result to returnrun_query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as \"the user\" or \"a buyer\".",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[]New value: +[
      +  "context"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, non-external read operation. The description adds useful scope by specifying only the signed-in user's connected repositories, but it does not discuss pagination, default limits, or removed repositories beyond what the schema exposes.

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?

The definition is a single front-loaded sentence with no wasted wording. It could be slightly more action-oriented, but it communicates the resource and scope efficiently.

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 list tool with a rich input schema and no output schema, the description supplies the essential scope and purpose. The main remaining gap is explicit routing guidance relative to sibling query tools, but it is otherwise sufficient to call the tool correctly.

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 description coverage is high at 83%, and the schema documents sort, limit, filter, offset, context, and result_type. The description adds no additional meaning about these parameters, so the baseline of 3 is appropriate.

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 states a clear resource and scope: GitHub repositories connected by the signed-in user, with a sale-related purpose. It does not explicitly distinguish this from nearby query tools such as search_codebases, so it falls short of full sibling differentiation.

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?

The phrase 'which they can list for sale' implies this is used before creating a listing, but the description does not explicitly state when to use it versus alternatives or when not to use it.

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