Skip to main content
Glama

Search map events

search_map_events

Searches event names, notes, and optional command text across one map or all maps to locate dialogue, scripts, or plugin commands.

Instructions

Case-insensitive substring search across events on one map or every map. Matches event names and notes; with searchCommands=true it also searches inside event command parameters (message text, script lines, plugin commands). Returns {mapId, mapName, eventId, name, x, y, matchedIn}.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
mapIdNoSearch only this map; omit for all maps
queryYes
searchCommandsNoAlso search inside event command lists (slower, finds text/script content)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses case-insensitivity, which fields are matched (names, notes), that command-parameter search is an opt-in deeper mode, and the exact result shape. It does not state that the operation is read-only nor describe the default limit/pagination behavior.

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 tight sentences with zero filler: purpose first, then the matching scope, then the return shape. Every sentence earns its place.

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 4-param search tool with no annotations and no output schema, the description covers purpose, match targets, the opt-in deeper mode, and the return fields. The only real gap is result-count behavior (limit defaults to 50, max 200), which an agent would want to know before paging.

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 only 50% (query and limit lack descriptions), and the description compensates by clarifying that query is a case-insensitive substring and that mapId omission means all maps, plus what searchCommands actually reaches into. The limit parameter remains unexplained in both schema and description.

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 ('case-insensitive substring search across events') plus the scope (one map or every map), which immediately separates it from sibling search tools like search_records or find_usages that operate on different resources.

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?

Explains that omitting mapId searches every map and that searchCommands=true opts into deeper command-parameter searching, giving clear usage context. It stops short of explicitly naming the alternative tool to use when the agent wants records/plugins instead of events, so it lacks full when-not guidance.

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