Skip to main content
Glama

Search skills

search_skills
Read-onlyIdempotent

Search Ready skills by default, or select state=draft to search only this user's authored Drafts. Ready grants and requests do not apply to Drafts.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size. Defaults to 20.
queryNoOptional search text.
stateNoReturn governed Ready skills by default, or only Drafts authored by this user.
cursorNoOpaque cursor returned by the previous page.

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world behavior. The description adds a governance detail beyond them: grants and requests do not apply to Drafts, which is genuinely useful. It says nothing about pagination behavior or result ordering, so the added 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 default behavior front-loaded ahead of the exception. No filler, though the second sentence's phrasing about grants and requests is somewhat terse and could be clearer.

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?

With an output schema present, return values need not be explained, and all parameters carry schema descriptions. The Ready-versus-Draft scoping is covered adequately for a filtered search tool; only pagination/ordering expectations are left unstated.

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 four parameters (limit, query, state, cursor) are already documented in the schema, including the state enum and defaults. The description restates the state default rather than adding syntax or format detail beyond it, so the 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 ("Search ... skills") plus the scope distinction between default Ready skills and state=draft Drafts. It does not name sibling tools such as list_my_skills or get_skill, so differentiation from the catalog relies on the reader's knowledge of those names.

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

Usage Guidelines4/5

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

Gives clear operative context: searching Ready skills is the default, and state=draft narrows to only the user's authored Drafts. It does not state when to prefer this over list_my_skills or get_skill, so alternatives remain implicit.

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