Skip to main content
Glama

Open Agent Guide

List Capabilities

list_capabilities
Read-onlyIdempotent

List capabilities, optionally narrowed by search across names, verbose names, descriptions, and slugs. Pass a capability's slug to search_products to filter by it.

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_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque cursor from a previous page's response.
searchNoFree-text search across names, slugs, and text.
page_sizeNoResults per page (1-100).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 fully covered by structured data. The description adds workflow context (feed the slug to search_products) but says nothing about pagination behavior or result ordering, so incremental value is modest.

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 tight sentences with the core action front-loaded and the filter qualifier immediately after. The second sentence earns its place by routing the agent to the follow-up tool, with no filler.

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?

An output schema exists, annotations are rich, and all parameters are documented, so the description need not explain return values or safety. It is nearly complete, with only minor gaps around pagination expectations that the cursor parameter already implies.

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 100%, so all three parameters are already documented in the schema. The description slightly extends the search scope by naming 'verbose names' and 'descriptions', but adds no cursor or page_size semantics beyond what the schema states; baseline 3 applies.

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 capabilities') and immediately qualifies the scope with the optional search filter. It also names the downstream consumer (search_products), which helps distinguish its role from siblings like list_categories, though it does not explicitly contrast with them.

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?

It explains the optional narrowing behavior and tells the agent what to do with a returned slug, which implies the typical workflow. However, there is no explicit when-to-use versus when-not-to-use guidance relative to sibling list tools, so the usage guidance is inferred rather than stated.

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.

Resources