Skip to main content
Glama
riponcm

Projectmem

by riponcm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_events

Find past events by keyword in summaries and notes. Returns matching event types and timestamps, helping you locate a logged issue or decision before repeating it.

Instructions

Plain-text search across all logged events.

Token-efficient alternative to get_summary when you only need events
matching a keyword. Returns matching event summaries with type and
timestamp.

Read-only. Case-insensitive substring matching against each event's
summary and notes. Empty result returns a friendly message, not an
error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of matching events to return (most recent first). Defaults to 10. Recommended range: 1-100.
queryYesCase-insensitive substring matched against each event's summary and notes. Plain text only — no regex or boolean operators.
projectNoWhich project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • addedInput schema / properties / project
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Which project this call is about — a registered id, alias, or absolute path (e.g. 'ossdrop'). Omit it when the server was started for a single repo, or when an active project is set with `pjm project use`. Call list_projects to see the registered names.",
+  "title": "Project"
+}
  2. Changed4 schema fields changedv0.1.3
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of matching events to return (most recent first). Defaults to 10. Recommended range: 1-100."
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / query / description
      Added value: +"Case-insensitive substring matched against each event's summary and notes. Plain text only — no regex or boolean operators."
  3. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation is read-only, specifies case-insensitive substring matching against summary and notes, and explains that an empty result returns a friendly message rather than an error.

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?

The description is three short, front-loaded paragraphs. Every sentence adds value: the search scope, the alternative tool, the matching behavior, and the empty-result behavior. There is no filler or redundant restatement of the tool name.

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?

Given the 100% schema coverage and presence of an output schema, this description is complete enough for an agent to call the tool correctly. It explains the search scope, the matching rules, the read-only nature, and how empty results are handled.

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?

The schema already documents all parameters with 100% coverage. The description mostly restates the query semantics already present in the schema rather than adding new parameter-level meaning, so the baseline of 3 applies.

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 uses a specific verb and resource: 'Plain-text search across all logged events.' It also clearly states the return value (matching event summaries with type and timestamp) and distinguishes itself from get_summary, making its purpose unambiguous.

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

Usage Guidelines5/5

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

It explicitly names get_summary as the alternative and gives the condition for choosing this tool: when you only need events matching a keyword. This is direct, actionable usage guidance with no need for inference.

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