Skip to main content
Glama

Search Procedures

search_procedures
Idempotent

Search analyzed procedure names by literal text or regex to locate matching procedures deterministically and completely.

Instructions

Search every analyzed procedure name using literal matching by default or regex when requested. Results are deterministic and complete. Hopper regex mode uses ECMAScript Unicode syntax in a cancellable worker; a matching deadline leaves its API usable.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "literal",
      "pattern": "main",
      "case_sensitive": false
    },
    "name": "search_procedures"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoOperation mode that selects the requested behavior.
patternYesThe literal text or regex pattern to search for
documentNoThe document name
case_sensitiveNoWhether to match case

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Adds real behavioral context beyond the annotations: deterministic, complete results, an ECMAScript Unicode regex dialect, execution in a cancellable worker, and that a matching deadline leaves the underlying API usable. However, it never reconciles these read-like semantics with readOnlyHint=false, so an agent cannot tell whether the call mutates state (index/cache) and whether it is safe to repeat.

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?

Three compact sentences, front-loaded with what is searched and the matching-mode default. The implementation note about the worker and deadline is dense but earns its place for anyone writing regex; no filler sentences.

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?

For a four-parameter search tool with no output schema, the description covers mode selection, match dialect, determinism guarantees, and cancellation behavior. Given the annotation coverage and the fully-described schema, this is sufficient for an agent to call it 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 the baseline is 3. The description restates that 'pattern' accepts literal text or a regex and that literal is the default mode, but adds no syntax detail, escaping rules, or meaning for 'document' and 'case_sensitive' beyond what the schema already provides.

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 every analyzed procedure name') plus the two matching modes, so the agent knows exactly what is being queried and against which domain (procedure names, not strings or classes). It does not name a sibling such as list_procedures or search_strings to sharpened the boundary, which keeps it below a 5.

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?

The default-selection rule is stated ('literal matching by default or regex when requested'), which tells the agent how to choose the mode. There is no guidance on when to use this versus list_procedures or the other search_* tools, and no prerequisites or exclusions, so usage is only implied.

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

Deploy Server

Other Tools