Skip to main content
Glama
Repo Test Architect

Repo Test Architect

List Adapters

list_adapters
Read-onlyIdempotent

Lists registered language adapters available for repository audits, showing which ecosystems the test architecture audit can inspect.

Instructions

List registered language adapters available to audit repositories.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
adaptersYes
schemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.0
    • removedOutput schema / $id
      Removed value: -"adapter-registry-v1.schema.json"
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / description
      Added value: +"Top-level shape of this artifact. The complete contract is schemas/adapter-registry-v1.schema.json in the published package."
    • removedOutput schema / properties / adapters / items
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "ecosystems": {
      -      "items": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "minItems": 1,
      -      "type": "array"
      -    },
      -    "emittedArtifacts": {
      -      "items": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "minItems": 1,
      -      "type": "array"
      -    },
      -    "id": {
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    "languages": {
      -      "items": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "minItems": 1,
      -      "type": "array"
      -    },
      -    "maturity": {
      -      "enum": [
      -        "supported",
      -        "experimental",
      -        "planned"
      -      ]
      -    },
      -    "supportedProjectTypes": {
      -      "items": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "supportedTestFrameworks": {
      -      "items": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "id",
      -    "ecosystems",
      -    "languages",
      -    "maturity",
      -    "supportedTestFrameworks",
      -    "supportedProjectTypes",
      -    "emittedArtifacts"
      -  ],
      -  "type": "object"
      -}
    • removedOutput schema / title
      Removed value: -"Adapter Registry Artifact"
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$id": "adapter-registry-v1.schema.json",
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "adapters": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "ecosystems": {
      +            "items": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "minItems": 1,
      +            "type": "array"
      +          },
      +          "emittedArtifacts": {
      +            "items": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "minItems": 1,
      +            "type": "array"
      +          },
      +          "id": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "languages": {
      +            "items": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "minItems": 1,
      +            "type": "array"
      +          },
      +          "maturity": {
      +            "enum": [
      +              "supported",
      +              "experimental",
      +              "planned"
      +            ]
      +          },
      +          "supportedProjectTypes": {
      +            "items": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "supportedTestFrameworks": {
      +            "items": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "ecosystems",
      +          "languages",
      +          "maturity",
      +          "supportedTestFrameworks",
      +          "supportedProjectTypes",
      +          "emittedArtifacts"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "schemaVersion": {
      +      "const": "adapter-registry/v1"
      +    }
      +  },
      +  "required": [
      +    "schemaVersion",
      +    "adapters"
      +  ],
      +  "title": "Adapter Registry Artifact",
      +  "type": "object"
      +}
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the narrow nuance that the list is limited to *registered* adapters, and says nothing about ordering, filtering, or whether the registry can change between calls.

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 front-loaded sentence with no filler and no repetition of the title. It is efficient, though on the thin side — one more clause on when to reach for it would have cost little.

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?

Complexity is low (no params, output schema present, safety covered by annotations), so little is required. Still, the description never explains what an 'adapter' represents in this system or how the returned list relates to the sibling audit tools, leaving the agent to guess the follow-up action.

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 the baseline is 4. The description correctly implies no input is needed and does not invent filtering options that the empty schema cannot honor.

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 gives a specific verb+resource: 'List registered language adapters', with the added qualifier that these are the adapters 'available to audit repositories'. That is clearly distinct from the analysis/audit siblings, which operate on repositories rather than on the adapter registry. It stops short of naming a sibling alternative, but the resource 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 phrase 'available to audit repositories' hints this is a discovery/prerequisite call before auditing, but there is no explicit when-to-use, no exclusion, and no pointer to analyze_repository or audit_repo as the downstream step. An agent can infer the purpose but is given no routing guidance.

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