Skip to main content
Glama

caps-list_capabilities

Lists capability modules from a project's cap-manifest.json, including qualified names, provided services and versions, lifecycle owner, and manifest initOrder; returns an empty list when none exist.

Instructions

List the capability modules composed into this project, from the build-time cap-manifest.json: each module's qualified name, the services it provides with their versions, and which module owns the lifecycle. Also returns initOrder exactly as the manifest states it. A project with no capabilities returns an empty list, not an error.

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": "caps-list_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose useful traits: the data source is the build-time manifest, empty projects return an empty list rather than an error, and initOrder is returned verbatim without normalization. It does not say whether results are cached, whether a missing manifest is an error, or how stale the build-time data can be — meaningful gaps for a tool with zero annotation coverage.

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?

Three sentences, front-loaded with the action and the data source, followed by two specific caveats. The first sentence is long and packs three returned fields into one clause, but nothing is redundant or padded.

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?

There is no output schema and no annotations, so the description must describe the return shape itself, which it does by naming the fields and the initOrder component. What remains underspecified is failure behavior beyond the empty-project case and the freshness of the build-time manifest.

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; the baseline applies. It correctly avoids inventing filtering options that do not exist, keeping expectations aligned with the empty 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 and resource ('List the capability modules composed into this project') and enumerates what each entry contains: qualified name, provided services with versions, and lifecycle-owning module. The scope is unambiguous. It does not explicitly distinguish itself from the sibling caps-describe_composition, which is the only real gap.

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 'List ... from the build-time cap-manifest.json', which frames it as a bulk inventory read rather than a single-item describe. It gives no explicit when-to-use vs when-not-to-use, and never names an alternative such as caps-describe_composition for detail on one module.

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