Skip to main content
Glama

search

Find relevant knowledge entries across authorized namespaces using filters and a byte budget, returning only a small bundle for task context.

Instructions

Search authorized namespaces with filters and a byte budget.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
cursorNo
filtersNo
max_bytesNo
max_resultsNo
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose two meaningful traits beyond the schema surface: results are limited to namespaces the actor is authorized for, and output volume is capped by a byte budget. It omits what happens on budget exhaustion (truncation vs. error), pagination/cursor semantics, and result ordering.

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?

A single front-loaded sentence with no filler or redundancy; the core scope is stated first. It is efficient, though its terseness shifts the missing detail problem onto the completeness dimension rather than being a structural flaw.

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

Completeness2/5

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

For a tool with 6 parameters, a nested 9-field filter object, zero schema descriptions, and no annotations, one sentence is far too thin. The presence of an output schema removes the need to explain return values, but query syntax, filter semantics, pagination and byte-budget behavior remain undocumented.

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

Parameters2/5

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

Schema description coverage is 0% across 6 parameters, so the description must compensate and largely does not. It gestures at 'filters' and 'byte budget' (mapping to filters/max_bytes) but gives no meaning for query syntax, cursor, max_results, or actor_handle, and nothing about the 9-field nested SearchFilters object.

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 states a specific verb and resource ('Search authorized namespaces') plus the two main dimensions of control (filters, byte budget), so an agent knows this is a retrieval/query tool. It does not distinguish itself from retrieval siblings such as get_entry or get_context, leaving the boundary to be inferred.

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?

'Search authorized namespaces with filters' implies the condition for use (lookup by query across scoped namespaces), but there is no explicit when-to-use, when-not-to-use, or named alternative such as get_entry for direct ID lookup.

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