Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official
by RedHatInsights
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List repositories with filtering and pagination options.

content-sources__list_repositories
Read-only

List repositories with filtering and pagination options.

Instructions

List repositories with filtering and pagination options.

šŸŸ¢ CALL IMMEDIATELY - No information gathering required.

Each repository is a summary (identity, URL, origin, distribution, counts, and status). GPG keys, snapshots, and introspection details are omitted. Use get_repository for one UUID.

Input Schema

NameRequiredDescriptionDefault
urlNoFilter by repository URL (case-insensitive).
archNoFilter by architecture (e.g., 'x86_64', 'aarch64').
nameNoFilter by repository name (case-insensitive).
limitNoMaximum number of repositories to return (default: 10, maximum: 100). **ALWAYS use the default value of 10 for the first call.** This default is carefully chosen for performance and context management. Only increase this value if the user explicitly asks to see more repositories at once.
offsetNoNumber of repositories to skip for pagination (default: 0).
originNoFilter by origin (e.g., 'red_hat', 'external').
enabledNoFilter by enabled status (True/False).
versionNoFilter by version (e.g., '8', '9').
content_typeNoFilter by content type (e.g., 'rpm', 'ostree').

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.0.25
    • removedInput schema / properties / include_gpg_key
      Removed value: -{
-  "default": false,
-  "description": "Include GPG key content in the response (default: False).",
-  "type": "boolean"
-}
  2. Changed2 schema fields changedv0.0.10
    • addedInput schema / properties / include_gpg_key
      Added value: +{
+  "default": false,
+  "description": "Include GPG key content in the response (default: False).",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of repositories to return (default: 10)."New value: +"Maximum number of repositories to return (default: 10, maximum: 100). **ALWAYS use the default value of 10 for the first call.** This default is carefully chosen for performance and context management. Only increase this value if the user explicitly asks to see more repositories at once."
  3. First observedv0.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine behavioral context beyond that: what each returned item contains (identity, URL, origin, distribution, counts, status) and what is deliberately omitted (GPG keys, snapshots, introspection details). It does not mention auth/permission requirements or rate limits, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, followed by the call directive and the return-content caveats; every sentence carries information. The emoji callout is a little gimmicky but does not waste much space.

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 9-parameter read-only list tool with a 100%-covered schema, full annotations, and an output schema, the description supplies the routing rule, the call directive, and the omitted-fields caveat. It is essentially complete; only auth/permission context is absent.

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 100%, so all nine filter/pagination parameters are already documented in the schema (including the strong 'ALWAYS use the default of 10' guidance on limit). The description only summarizes them as 'filtering and pagination options' and adds no syntax or format detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('repositories') and adds scope ('filtering and pagination options'). It also distinguishes itself from the sibling get_repository ('Use get_repository for one UUID'), so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicitly tells the agent to 'CALL IMMEDIATELY - No information gathering required', and names the alternative tool (get_repository) with the condition that selects it (a single UUID). This is both a when-to-use directive and a when-to-use-the-other-tool rule.

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

Deploy Server

Other Tools