Skip to main content
Glama

search_context

Search stored memories and skills by full-text query to locate relevant context; returns matching slugs, names, descriptions, and snippets with best matches first.

Instructions

Full-text search across the user's memories and skills. Returns slug, name, description and a snippet, best match first.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior beyond the name: the fields returned (slug, name, description, snippet) and that results are ranked 'best match first'. It says nothing about matching semantics, whether both kinds are searched by default, or permission scoping.

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?

Two tight sentences: scope first, return contract second. Every clause carries information and nothing is padded.

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 three-parameter read-only search with no output schema, the description covers scope, result fields, and ordering — enough to call it correctly. The gaps are minor (default result count and whether kind filters or unions), but they exist.

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% for three parameters, and the description adds no meaning for any of them. The 'kind' enum values are self-describing and 'limit' has a default/max in the schema, but the query string's full-text behavior, the 300-char cap, and whether kind is optional are all left to the agent to infer.

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: 'Full-text search across the user's memories and skills', which clearly distinguishes it from direct readers like read_memory/read_skill and from search_tools (tools, not memories/skills). It stops short of naming those siblings explicitly, so it sits just below the top band.

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

Usage Guidelines2/5

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

The description never says when to choose this over read_memory, read_skill, or search_tools — e.g. 'use when you don't know the slug'. Discovery-by-text usage is only weakly implied by 'full-text search'; there are no exclusions or alternatives named.

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