Skip to main content
Glama

match_capabilities

Read-onlyIdempotent

Find active capabilities using hard price, timeout, runtime, category and input-schema filters. Ranking is lexical and deterministic, not semantic reasoning. Availability is a short-lived provider self-report, not a guarantee.

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

Input Schema

NameRequiredDescriptionDefault
inputNoOptional proposed JSON input; omit to skip schema check
limitNo
queryNoLiteral phrase
runtimeNo
categoryNoCapability category
max_priceNo
online_onlyNo
max_timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description adds real context beyond them: ranking is lexical/deterministic rather than semantic, and availability is a short-lived provider self-report that is not a guarantee. These caveats materially change how an agent should interpret and trust results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, zero filler. The capability statement comes first, followed by the two interpretive caveats (ranking method, availability trustworthiness) in decreasing order of importance, so an agent can stop reading after any sentence and still act correctly.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does not — no mention of result shape, whether prices or scores are returned, or how many items a limit yields. Behavioral trust caveats are well covered, but an agent still doesn't know what a successful response looks like.

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 only 38% across 8 parameters. The description names the filter families (price, timeout, runtime, category, input schema) and characterizes them as hard constraints, which sharpens meaning beyond the field names, but it says nothing about limit, online_only, or how query interacts with the lexical ranking — the very parameters where a low-coverage schema needs help most.

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 ('Find active capabilities') and enumerates the filter dimensions (price, timeout, runtime, category, input-schema), so the agent knows exactly what kind of lookup this is. It does not name or differentiate itself from the sibling 'search_capabilities', so the boundary between the two must be inferred from the words 'hard ... filters' versus 'lexical' ranking.

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 rather than stated: 'hard' filters plus 'lexical and deterministic, not semantic reasoning' hints this is for structured constraint matching rather than fuzzy search, but the description never says when to prefer it over search_capabilities or when not to use it. The only explicit conditional is inline in the schema ('omit to skip schema check').

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