Skip to main content
Glama

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "palim_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoFilter by metadata tags (match any).
limitNoMaximum number of results (default: 5)
queryNoKeyword 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. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Full-text search query. Omit for tags-only or project-only filtering."New value: +"Keyword search query. Omit for tags-only or project-only filtering."
  2. 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."
  3. 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"
      +}
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds real behavioral detail beyond that: what the query actually matches against (session text vs memory content/id) and case-insensitive project matching. It says nothing about result ordering, how sessions and memories are merged in the response, or limit behavior — though an output schema exists, so return shape is partly covered elsewhere.

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 tight sentences, front-loaded with the core action before the filtering details, with no filler or restated title. The only mild redundancy is listing tag/project/status/tool_source, which the schema already names.

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?

All six parameters are optional and fully documented in the schema, an output schema exists, and annotations cover the safety profile, so the remaining burden is small. The description handles the key ambiguity (query-less filtering) and the dual session/memory search scope; only cross-result ordering and merge semantics are left unaddressed.

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 coverage is 100%, so the baseline is 3. The description does add meaning for `query` — clarifying that it matches session text or memory content/id rather than a single corpus — and explains cross-field interaction (query optional when tags/project supplied). The remaining params are simply enumerated, adding little over 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 and resource ("Search saved sessions and memories") and clarifies the matching surface: query hits session text or memory content/id. It does not name any sibling (e.g. palim_get_context, palim_resume) to distinguish the search path from retrieval-by-id paths, so it stops short of a 5.

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

Usage Guidelines3/5

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

Gives one concrete usage rule — omit query for tags-only or project-only session filtering — which resolves the main operational ambiguity of a 0-required-parameter tool. It offers no guidance on when to prefer this over sibling read tools like palim_get_context or palim_resume, so usage is only partially framed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.