Skip to main content
Glama

search

Read-only

Find text patterns across a WordPress site's theme and plugin files using regex, with glob filters to narrow results by filename and optional case-insensitive matching.

Instructions

Regex search across files (like grep). glob filters file names, e.g. '*.php'.

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": {
      "pattern": "<pattern>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
globNo
pathNo.
siteNo
patternYes
ignore_caseNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully clarifies that matching is regex rather than literal, but it says nothing about max_results truncation, ignore_case behavior, the path default of '.', or what site scoping does — meaningful gaps for a search that can silently cap results.

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 short sentences, front-loaded with the core operation and free of padding. The terseness is efficient, though it comes at the cost of the missing parameter context rather than from deliberate prioritization.

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?

A six-parameter tool with no schema descriptions, no output schema, and no annotation-level detail beyond the read-only flag needs more than two sentences. An agent cannot tell from this definition what path/site do, whether max_results silently truncates, or how results are returned.

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%, so the description must carry the parameter burden, yet it only explains glob (with an example) and implies pattern via 'regex'. Four of six parameters — path, site, ignore_case, max_results — receive no meaning at all from the description.

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 ('Regex search across files') and anchors it to a familiar analogue ('like grep'), so an agent can distinguish it from read_file, list_dir, and stat. It stops short of naming which sibling to pick instead, but the operation itself is unambiguous.

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 grep analogy implies the use case (find content matching a pattern across a tree) but there is no explicit when-to-use or when-not-to-use guidance, no mention of when to prefer read_file or list_dir, and no prerequisite or scoping notes.

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