Skip to main content
Glama

Projects Search

projects_search
Read-onlyIdempotent

Paginate or filter Repology projects by name substring, maintainer, category, or repository membership; returns up to 200 project names per page with their per-repo version data.

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": {
      "search": "python"
    },
    "name": "projects_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo1-200 (default 50).
searchNoSubstring match on project name.
in_repoNoRestrict to one repo, e.g. "alpine_edge".
categoryNo
end_nameNoPagination cursor, project name to end at (reverse).
maintainerNo
start_nameNoPagination cursor, project name to start at.
not_in_repoNoExclude one repo.

Output Schema

NameRequiredDescriptionDefault
countYesNumber of matched projects returned.
itemsYesOne row per matched project, regrouped from Repology's name->rows map into the catalog's standard items/count shape

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / end_name / description
      Previous value: -"Pagination cursor — project name to end at (reverse)."New value: +"Pagination cursor, project name to end at (reverse)."
    • changedInput schema / properties / start_name / description
      Previous value: -"Pagination cursor — project name to start at."New value: +"Pagination cursor, project name to start at."
  2. Changed9 schema fields changed
    • changedOutput schema / properties / count / description
      Previous value: -"Number of items returned."New value: +"Number of matched projects returned."
    • changedOutput schema / properties / items / description
      Previous value: -"Paginated list of projects matching search criteria"New value: +"One row per matched project, regrouped from Repology's name->rows map into the catalog's standard items/count shape"
    • addedOutput schema / properties / items / items / additionalProperties
      Added value: +true
    • removedOutput schema / properties / items / items / properties / latest_version
      Removed value: -{
      -  "description": "Latest available version",
      -  "type": "string"
      -}
    • removedOutput schema / properties / items / items / properties / name
      Removed value: -{
      -  "description": "Project name",
      -  "type": "string"
      -}
    • addedOutput schema / properties / items / items / properties / packages
      Added value: +{
      +  "description": "This project's per-repository package rows, as Repology's own API returns them",
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "categories": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "licenses": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "maintainers": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "origversion": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "repo": {
      +        "type": "string"
      +      },
      +      "srcname": {
      +        "type": "string"
      +      },
      +      "status": {
      +        "type": "string"
      +      },
      +      "subrepo": {
      +        "type": "string"
      +      },
      +      "summary": {
      +        "type": "string"
      +      },
      +      "version": {
      +        "type": "string"
      +      },
      +      "visiblename": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / items / items / properties / project
      Added value: +{
      +  "description": "Project name (Repology's own map key for this match)",
      +  "type": "string"
      +}
    • removedOutput schema / properties / items / items / properties / repos
      Removed value: -{
      -  "description": "Repositories containing this project",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / items / items / properties / status
      Removed value: -{
      -  "description": "Overall project status",
      -  "type": "string"
      -}
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "search": "python"
      +  },
      +  {
      +    "count": 30,
      +    "in_repo": "alpine_edge"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Number of items returned.",
      +      "type": "integer"
      +    },
      +    "items": {
      +      "description": "Paginated list of projects matching search criteria",
      +      "items": {
      +        "properties": {
      +          "latest_version": {
      +            "description": "Latest available version",
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "Project name",
      +            "type": "string"
      +          },
      +          "repos": {
      +            "description": "Repositories containing this project",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "status": {
      +            "description": "Overall project status",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "items",
      +    "count"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results are paged at up to 200 names with per-repo version data, but says nothing about ordering, filter combination logic, rate limits, or behavior when a filter matches nothing — and the output schema already covers the return shape.

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 semicolon-joined sentence that front-loads the action, then the filter axes, then the return payload. Dense but every clause carries information; no filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, no required fields, an output schema and full annotations, the description covers the core contract but leaves real gaps: result ordering, whether multiple filters intersect, and how the name-based pagination cursors are meant to be used. Adequate but not complete for a tool of this parameter surface.

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 75%, which sets the baseline at 3. The description reinforces the count ceiling ('up to 200 ... per page') and groups in_repo/not_in_repo under 'repository membership', but it never explains the start_name/end_name cursor semantics, which are the least self-explanatory parameters in 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?

States a specific verb set (paginate/filter) and a specific resource (Repology projects), then enumerates the filter dimensions and the return payload. It is clear enough to distinguish from most siblings, though it never names or contrasts any related search tool such as search_within.

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 verb 'paginate or filter' implies the intended usage context, and the mention of pagination signals this is the traversal tool for a project list. However, there is no explicit when-to-use/when-not guidance, no statement about combining filters, and no named alternative for full-text or cross-entity search.

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.