Skip to main content
Glama

search_capabilities

Read-onlyIdempotent

Discover versioned executable AI capabilities. Each manifest defines validated inputs/outputs, fixed price in TRIAL credits, runtime, timeout and execution-only license. Provider availability is not guaranteed.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch capability or requirement
offsetNo
categoryNoExact category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description goes beyond them by disclosing what a result contains (validated I/O, fixed price in TRIAL credits, runtime, timeout, execution-only license) and that provider availability is not guaranteed — a genuinely non-obvious behavioral caveat. It omits matching/ranking semantics and result ordering.

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 tight sentences, front-loaded with the purpose and followed by result semantics and a caveat; no filler. The middle sentence is information-dense and earns its place. Minor cost: the credential/licensing detail is packed into one long clause.

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?

There is no output schema, so the description is the only place result shape could be explained — it gestures at it (manifest fields) but does not describe the result envelope, pagination, or empty-result behavior. For a zero-required-parameter discovery tool with an open-world hint, it is adequate but leaves real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description says nothing about any of the three parameters. With 67% schema coverage, q and category are described in the schema, but offset is undocumented anywhere beyond its numeric bounds, and the description never explains pagination, default result count, or how q is matched. It does not compensate for the coverage gap.

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 opens with a specific verb+resource: "Discover versioned executable AI capabilities" — an agent reading it knows this is the capability-lookup tool in a marketplace that also has search_requests and search_services. It does not explicitly name those siblings, so differentiation is inferred from the noun rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says to call this before quote_capability or start_run, nor that get_capability exists for retrieval by id. The availability caveat hints that results still need verification, but that is a warning, not usage guidance.

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