Skip to main content
Glama

Repositories

repositories
Read-onlyIdempotent

List the package repositories indexed by Repology (distros, BSDs, language ecosystems, etc.) with per-repository project counts: total, newest, outdated, unique, problematic, potentially vulnerable, plus the number of maintenance problems. Read from Repology's published repository statistics.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYesRepositories with project statistics

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • changedOutput schema / properties / items / description
      Previous value: -"Array of repositories with stats and status"New value: +"Repositories with project statistics"
    • changedOutput schema / properties / items / items / properties / name / description
      Previous value: -"Repository name"New value: +"Repository id"
    • removedOutput schema / properties / items / items / properties / num_maintainers
      Removed value: -{
      -  "description": "Number of maintainers in repository",
      -  "type": "number"
      -}
    • addedOutput schema / properties / items / items / properties / num_newest
      Added value: +{
      +  "description": "Projects at the newest version",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / items / items / properties / num_non_unique
      Added value: +{
      +  "description": "Non-unique projects",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / items / items / properties / num_outdated
      Added value: +{
      +  "description": "Outdated projects",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / items / items / properties / num_packages / description
      Previous value: -"Number of packages in repository"New value: +"Projects packaged in this repository"
    • changedOutput schema / properties / items / items / properties / num_packages / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • addedOutput schema / properties / items / items / properties / num_problematic
      Added value: +{
      +  "description": "Problematic projects",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / items / items / properties / num_problems / description
      Previous value: -"Number of problems in repository"New value: +"Maintenance problems"
    • changedOutput schema / properties / items / items / properties / num_problems / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
    • addedOutput schema / properties / items / items / properties / num_unique
      Added value: +{
      +  "description": "Projects unique to this repository",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / items / items / properties / num_vulnerable
      Added value: +{
      +  "description": "Potentially vulnerable projects",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • removedOutput schema / properties / items / items / properties / state
      Removed value: -{
      -  "description": "Repository status",
      -  "type": "string"
      -}
    • addedOutput schema / properties / items / items / properties / title
      Added value: +{
      +  "description": "Repository display name",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Number of items returned.",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "description": "Array of repositories with stats and status",
      +      "items": {
      +        "properties": {
      +          "name": {
      +            "description": "Repository name",
      +            "type": "string"
      +          },
      +          "num_maintainers": {
      +            "description": "Number of maintainers in repository",
      +            "type": "number"
      +          },
      +          "num_packages": {
      +            "description": "Number of packages in repository",
      +            "type": "number"
      +          },
      +          "num_problems": {
      +            "description": "Number of problems in repository",
      +            "type": "number"
      +          },
      +          "state": {
      +            "description": "Repository status",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "items",
      +    "count"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, non-destructive, and open-world, so the safety profile needs no restating. The description adds that it reads Repology's *published* repository statistics, hinting the data is a derived snapshot rather than live queries, but it says nothing about freshness, caching, or result size.

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?

Two sentences, front-loaded with the verb and resource before the metric list, with no filler. The long enumeration of counts is dense but content-bearing, though it partially anticipates the output schema.

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?

With no parameters, full annotation coverage, and an output schema present, the description only needed to say what the resource is and where the data comes from, both of which it does. Repeating the returned metrics is mild redundancy against the output schema but leaves no gap for an agent deciding whether to call it.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The empty schema is consistent with the description, which presents this as an unfiltered enumeration of all repositories.

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 and resource ('List the package repositories indexed by Repology') and then scopes the resource with concrete examples ('distros, BSDs, language ecosystems'). It does not explicitly contrast itself with related siblings such as 'problems', but the object of the operation is unambiguous.

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?

Usage is only implied: the description frames the tool as an enumeration of repositories and their statistics, which suggests it is a discovery/overview call. There is no statement of when to prefer it over a related tool, no prerequisites, and no exclusions.

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.