Skip to main content
Glama

Physical Capability Cloud

search_capabilities

Read-only

List the built-in capability type templates: each type's name, version, description, parameter count, parameter group names and a base price hint. NOTE: these describe types, not operators' offerings, and carry no assurance tiers or availability. The gateway does not read the query, so it never narrows the list. Registered capabilities of a type are listed by GET /api/capabilities?type=.

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
queryNoOptional and not used: the gateway returns the full list whatever you send.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Search query (type name, material, process, etc.)"New value: +"Optional and not used: the gateway returns the full list whatever you send."
    • changedInput schema / required
      Previous value: -[
      -  "query"
      -]New value: +[]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety case is covered; the description adds genuinely new behavior: the gateway ignores the query parameter and always returns the full list, and the records contain no assurance tiers or availability data. That tells the agent what it cannot learn from this tool, which prevents false inference. It does not discuss ordering, volume, or pagination.

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 sentences, front-loaded with what the tool returns and followed by the caveat about scope. The query-ignoring point is duplicated between description and schema, but the description provides the reason (which the schema lacks), so the repetition is largely justified.

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?

No output schema exists, so the description carries the burden of describing the return shape, and it does so field by field. It also flags the absences (no assurance tiers, no availability) and the no-filtering behavior. Missing only ancillary details such as ordering or result volume.

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?

There is a single optional parameter and schema coverage is 100%, with the schema already stating it is 'Optional and not used'. The description restates the same fact ('the gateway does not read the query, so it never narrows the list'), which reinforces rather than extends schema meaning. Baseline 3 for a fully documented parameter.

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 and resource ('List the built-in capability type templates') and enumerates the returned fields (name, version, description, parameter count, parameter group names, base price hint). It also draws a clear boundary between type templates and registered/operator offerings, which separates it from creation or matching tools. It stops short of naming a sibling tool as the alternative, referring instead to a raw endpoint.

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 context is implied rather than stated: the NOTE tells the agent these results carry no assurance tiers or availability, and it redirects to GET /api/capabilities?type=<type> for registered capabilities. That is useful routing, but the alternative is an HTTP path rather than one of the available tools, and there is no explicit 'use this when / not when' framing.

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.