Skip to main content
Glama

There's An AI For That

Search repositories

search_repositories
Read-only

Search AI repositories by name, description, README, topics, owner, or linked TAAFT company. Results rank relevant, popular, official repositories first unless a sort is selected.

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": "search_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance
limitNo
ownerNoExact source owner, such as anthropics.
queryNoOptional repository name, capability, topic, owner, or README keywords.
companyNoExact linked TAAFT company slug.
licenseNoRepository license.
languageNoPrimary programming language.
min_starsNoMinimum GitHub star count.
updated_afterNoOnly repositories updated on or after this YYYY-MM-DD date.

Output Schema

NameRequiredDescriptionDefault
repositoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "Exact linked TAAFT company slug.",
      +  "type": "string"
      +}
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Primary programming language.",
      +  "type": "string"
      +}
    • addedInput schema / properties / license
      Added value: +{
      +  "description": "Repository license.",
      +  "type": "string"
      +}
    • addedInput schema / properties / min_stars
      Added value: +{
      +  "description": "Minimum GitHub star count.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / owner
      Added value: +{
      +  "description": "Exact source owner, such as anthropics.",
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"AI repository name or company to search for."New value: +"Optional repository name, capability, topic, owner, or README keywords."
    • addedInput schema / properties / sort
      Added value: +{
      +  "default": "relevance",
      +  "enum": [
      +    "relevance",
      +    "stars",
      +    "latest",
      +    "recently_updated"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / updated_after
      Added value: +{
      +  "description": "Only repositories updated on or after this YYYY-MM-DD date.",
      +  "format": "date",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "query"
      -]
    • addedOutput schema / properties / repositories / items / properties / company
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "id": {
      +      "type": "integer"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "slug": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "name",
      +    "slug",
      +    "url"
      +  ],
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / repositories / items / properties / description / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • addedOutput schema / properties / repositories / items / properties / forks
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / repositories / items / properties / github_url
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / repositories / items / properties / language
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / repositories / items / properties / license
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / repositories / items / properties / owner
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / repositories / items / properties / source_url
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / repositories / items / properties / stars
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / repositories / items / properties / updated_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / repositories / items / required
      Previous value: -[
      -  "id",
      -  "entity_type",
      -  "name",
      -  "slug",
      -  "url"
      -]New value: +[
      +  "id",
      +  "entity_type",
      +  "name",
      +  "slug",
      +  "url",
      +  "description",
      +  "stars",
      +  "forks",
      +  "language",
      +  "license",
      +  "updated_at",
      +  "source_url",
      +  "github_url",
      +  "owner",
      +  "company"
      +]
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds genuine behavioral information beyond that: default ranking prefers relevant, popular, and official repositories unless a sort is explicitly selected. It still omits result-set shape and pagination, but that is largely covered by the output schema.

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, zero filler, with the searchable scope front-loaded and the ranking caveat second. Every clause carries meaning.

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?

With an output schema present, return values need no explanation, and the description covers what is searchable and how results are ordered. The main omission is guidance on whether query is required and how this differs from get_repository, but for a 9-parameter read-only search tool this is close to complete.

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 78%, so the schema already documents most parameters (owner, company, query, license, language, min_stars, updated_after). The description's field list loosely maps to the query parameter's semantics but adds no syntax, format, or matching-behavior detail beyond the schema. Baseline 3 is appropriate.

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 (Search) plus resource (AI repositories) and enumerates exactly which fields are searched (name, description, README, topics, owner, linked TAAFT company). This clearly separates it from the get_repository sibling and from other search_* tools.

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 implied by the search_* naming family, but the description never says when to use this versus get_repository for detail, nor whether a query is required to get results (query is optional in the schema). It does note that sort changes the ranking behavior, which is a partial hint.

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.