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

TableJSON 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

TableJSON 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

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavior beyond that: what gets searched, that query matches both session text and memory content/id, that metadata filtering is supported, and that project matching is case-insensitive. This gives the agent useful behavioral context without contradicting annotations.

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 sentences with no filler. The main purpose is front-loaded, followed by matching semantics and practical usage guidance. Every sentence earns its place.

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?

For a read-only search tool with zero required parameters, an output schema, and full schema description coverage, this description is complete. It covers the search domain, matching behavior, filter options, and special usage cases. The agent has everything needed to invoke it correctly.

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 100%, so the baseline is 3. The description adds value beyond the schema by explaining the query's matching scope, the relationship between query omission and tag/project filtering, and the case-insensitivity of project matching. This clarifies parameter combinations that the schema alone does not convey.

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 opens with a specific verb and resource: 'Search saved sessions and memories.' It further clarifies what is matched ('session text or memory content/id') and enumerates filter dimensions, making the tool's purpose unmistakable and distinct from the sibling tools.

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?

The description gives clear usage context: query for full-text search, omit query for tags-only or project-only filtering, and notes case-insensitive project matching. It does not explicitly name alternatives or state when not to use this tool, but the intended invocation patterns are clear.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources