Skip to main content
Glama

Palim

by io.github.joleschmidt

palim_get_context

Read-onlyIdempotent

Get formatted context for a specific topic by searching and retrieving relevant sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoFilter by metadata tags (match any).
topicYesTopic to get context for.
statusNoOptional filter by metadata.status (e.g. "laufend", "abgeschlossen").
projectNoOptional filter by project
max_sessionsNoMaximum number of sessions to include (default: 3)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesHuman-readable tool result text.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+}
  2. 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 readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe read operation. The description adds that it aggregates sessions via search and retrieval to produce formatted context, which is a useful behavioral trait. However, it does not disclose criteria for selecting sessions or what 'formatted' entails beyond what annotations already imply.

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 a single sentence that is front-loaded with the core action ('Get formatted context') and includes the key mechanism ('by searching and retrieving relevant sessions'). Every word contributes, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of a detailed input schema and an output schema reduces the burden on the description. However, given the large set of sibling tools, the description does not clearly position when this tool should be preferred over similar retrieval tools like palim_find_similar or palim_get_sessions, leaving a completeness gap in tool selection guidance.

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 input schema provides descriptions for all 5 parameters, achieving 100% coverage, so the baseline is 3. The description 'specific topic' loosely maps to the required 'topic' parameter, but it adds no new semantic details about filtering, defaults, or interactions between parameters.

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?

The description uses a specific verb 'Get' and identifies the resource as 'formatted context for a specific topic', while explaining the mechanism of searching and retrieving relevant sessions. It is clear and distinct from mere session listing, but it does not explicitly contrast with sibling tools like palim_search or palim_get_sessions.

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?

The intended use for retrieving topic-specific context is implied, but there is no explicit guidance on when to use this tool versus alternatives such as palim_search or palim_get_user_context. No exclusions or preference conditions are given, so the agent must infer the right context from the name and description.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have distinct purposes, especially the save/delete actions and help. However, save_context vs save_session and get_context vs search overlap enough that an agent could select the wrong one without reading closely.

Naming Consistency4/5

All tools share the palim_ prefix and use snake_case, with a mostly consistent verb_noun pattern. help, resume, and search are verb-only names, which is a minor deviation from the otherwise predictable scheme.

Tool Count5/5

Nine tools is a well-scoped number for a memory and session management server. Each tool has a defined role, and there is no obvious bloat or excessive proliferation.

Completeness2/5

The save_session description explicitly references palim_update_session_metadata and palim_update_session_references, but those tools are not available, creating a workflow dead end. There is also no update/delete mechanism for stored memories, leaving notable lifecycle gaps.

Resources