Agentic Keychain

Search capabilities

search_capabilities

Read-onlyIdempotent

Search capability names, summaries, tasks and use-when conditions by keywords, ranked by lexical relevance only, never by payment. Use when: you want to see which capabilities exist for a topic, or you know part of a name. Not for: deciding whether one fits your task (resolve_task, or evaluate_capability for the full arithmetic) or reading a capability you can already name (get_capability). Input: search words, at most 500 characters; no earlier call is needed. Output: ak.search.v1 with id, name, summary, relevance, state, price and the strongest evidence label of each result, and no decision.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many results to return, from 1 to 50 (default 10).
`query`	Yes	Search words (at most 500 characters).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026
- addedInput schema / properties / limit / description
```
Added value: +"How many results to return, from 1 to 50 (default 10)."
```
First observedSep 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by disclosing that results are ranked by lexical relevance only, never by payment, and that an earlier call is not required. It also pre-empts a likely misreading by stating the output is 'no decision'. It does not discuss pagination or result-set limits beyond the schema.

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?

Dense but tightly organized into purpose, Use when, Not for, Input, and Output blocks, with the core action front-loaded. A few phrases are redundant with the schema (the 500-character restatement), but nothing is truly wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema present, the description compensates by naming the return type (ak.search.v1) and its fields, and it closes the loop by stating no decision is produced. Combined with the explicit routing guidance, an agent has everything needed to select and invoke this tool correctly.

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 query and limit are already documented in structured form; the description largely restates the 500-character query constraint and adds only the useful note that no prior call is needed. The limit parameter is not mentioned in the description at all. Baseline 3 is appropriate when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (capability names, summaries, tasks, use-when conditions) with a stated ranking rule. It explicitly distinguishes itself from named siblings get_capability, resolve_task, and evaluate_capability, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Contains explicit 'Use when:' and 'Not for:' clauses, each with the alternative tool to call instead (resolve_task, evaluate_capability, get_capability). The condition that selects this tool versus its siblings is fully spelled out.

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

All Agentic Keychain tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?