Skip to main content
Glama

Palim

by io.github.joleschmidt
OverviewDiscussionsAdmin

palim_search

Read-onlyIdempotent

Search saved sessions and memories. Query matches session text or memory content/id. Supports metadata filtering via tags/project/status/tool_source. Omit query for tags-only or project-only session filtering. Project match is case-insensitive.

Input Schema

NameRequiredDescriptionDefault
tagsNoFilter by metadata tags (match any).
limitNoMaximum number of results (default: 5)
queryNoFull-text search query. Omit for tags-only or project-only filtering.
statusNoOptional filter by metadata.status (e.g. "laufend", "abgeschlossen", "referenz", "archiviert").
projectNoOptional case-insensitive project filter (Logisoft ≡ logisoft). Allowed without query or tags.
tool_sourceNoOptional explicit filter by tool source (cursor, claude, chatgpt, web, etc.).

Output Schema

NameRequiredDescriptionDefault
messageYesHuman-readable tool result text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / project / description
      Previous value: -"Optional filter by project"New value: +"Optional case-insensitive project filter (Logisoft ≡ logisoft). Allowed without query or tags."
    • changedInput schema / properties / query / description
      Previous value: -"Full-text search query. Omit for tags-only filtering."New value: +"Full-text search query. Omit for tags-only or project-only filtering."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "description": "Human-readable tool result text.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "message"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety bar is low. The description adds genuinely new behavioral context: the query matches session text or memory content/id, and project matching is case-insensitive. It does not describe result ordering or how sessions and memories are merged in the result set.

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?

Four short sentences, front-loaded with purpose before filtering details, with no filler. Slightly dense but every sentence carries information.

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?

Output schema exists, so return-value explanation is unnecessary, and annotations cover the safety profile. For a read-only search over two resource types, the definition covers matching semantics and no-query modes; the one gap is how the two result types are combined or ordered.

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 and the schema already documents every parameter including case-insensitive project matching. The description repeats the case-insensitivity and adds matching-scope context for query, but contributes little beyond the schema.

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 (search) and the resources it covers (saved sessions and memories), plus what the query matches against. It does not name or differentiate from siblings like palim_get_context or palim_resume, but the scope is unambiguous from the text alone.

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?

Gives a concrete calling condition: 'Omit query for tags-only or project-only session filtering,' which tells the agent how to use the tool in filter-only mode. It stops short of saying when to prefer this over sibling retrieval tools such as palim_get_context.

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

All Palim toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources