Skip to main content
Glama

Search packs

search_packs
Read-onlyIdempotent

Search the Symbola registry for packs: software a coding agent can build from its decisions. Matches words against each pack's name, summary, id and category. With no query, lists every pack.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMost packs to return (default 10).
queryNoWords to look for, e.g. "paper library" or "encrypted meetings".
categoryNoOnly packs in this category: research, finance, text, data, places, time, dev, productivity or other.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, and closed-world behavior, so the bar is lower. The description adds valuable context beyond that: the fields searched and the empty-query listing behavior. It omits result ordering and whether all fields of a pack are returned, which keeps it from a 5.

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 compact sentences, front-loaded with the core action and scope. Every sentence carries distinct information; nothing is redundant with the title or schema.

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?

For a low-complexity search tool with full schema coverage and no output schema, the description covers purpose, matching behavior, and the empty-query case. It does not describe the shape or fields of returned packs, which would help an agent know what to expect.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that 'query' matches against name, summary, id, and category, which the schema's 'Words to look for' does not state.

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 and resource ('Search the Symbola registry for packs') and defines what a pack is. It also explains exactly which fields the query matches, making it distinguishable from get_pack, which retrieves a single pack.

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 usage context, including the important behavior that an empty query lists every pack (a browse mode). It does not name sibling tools like get_pack for direct retrieval, so the when-to-use-differently guidance is implied rather than explicit.

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