Skip to main content
Glama
Sign In
Protocol Chaos reference server

Protocol Chaos reference server

by chaos-xxl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

event_search

Read-only

Find existing events by query words before creating a new one, preventing duplicate matters. Search titles, facts, progress, and refs, with state filter and result limit.

Instructions

Find Events for a query you chose, such as the name of a matter, before creating one (so one matter does not become two). Matching is by words, not by meaning: every Event whose title contains the query (ignoring case) comes first, then Events whose facts, progress, refs or recorded words contain it, then Events that hold every word of the query. Returns {events} in brief, as in the directory, best matches first. Filter by state (a state, "open" or "closed"); limit caps the number returned.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesThe words to look for, such as the name of a matter.
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does well: it discloses that matching is lexical, not semantic, spells out the three-tier ranking order, and states results come 'in brief' with best matches first. It stops short of covering limits on result count or 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded, with the purpose and the create-avoidance rationale first, then matching semantics, then the two filters. The middle sentence is a long run-on, but every clause (rounding, ranking, return shape) carries information the agent needs, so nothing is padding.

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 3-param, read-only search with no output schema, the description covers the essentials: required query, both optional filters, ranking order, and a rough return shape ('{events} in brief'). Missing only edge details like default limit and whether results are paginated.

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 33% (query is documented, limit and state are not), so the description must compensate, and it largely does: it explains state as 'a state, "open" or "closed"' (clarifying the enum grouping) and that limit 'caps the number returned'. It omits default limit and the meaning of the individual states, leaving some gap.

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?

The description states a specific verb and resource ('Find Events for a query') and immediately frames the scope in a way an agent can distinguish from entity_search or event_get: it searches Events by text. The parenthetical use case ('before creating one') makes the role of the tool unmistakable.

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?

It gives a clear when-to-use condition ('before creating one, so one matter does not become two'), which is exactly the decision point an agent faces. It does not, however, name an alternative tool or an exclusion (e.g., when to prefer entity_search or event_get instead), so it falls short of the 5 rubric.

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