Skip to main content
Glama

Palim

by io.github.joleschmidt
OverviewDiscussionsAdmin

palim_get_context

Read-onlyIdempotent

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

Input 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

NameRequiredDescriptionDefault
messageYesHuman-readable tool result text.

Schema Changelog

Changes observed during successful MCP inspections.

  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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that the output is 'formatted context' assembled by searching and retrieving sessions, which is useful but modest; it says nothing about pagination, ordering, or how many results are returned when max_sessions is exceeded.

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?

A single front-loaded sentence that names the action, the output artifact, the scoping input, and the retrieval mechanism with no filler. Nothing in it is redundant.

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?

With an output schema present, full parameter coverage, and annotations covering the safety profile, the description does not need to explain return values or side effects. It is nearly complete for a 5-parameter retrieval tool; the only real gap is the unstated relationship to sibling retrieval tools like palim_search.

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 every parameter (tags, topic, status, project, max_sessions) is already documented in the schema with examples and a default. The description adds no syntax, format, or interaction detail beyond what the schema provides, making the baseline 3 correct.

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 states a specific verb (get) and resource (formatted context for a topic) and even describes the mechanism (searching and retrieving relevant sessions). It is clear on what the tool produces, but it does not distinguish it from siblings like palim_search or palim_get_brain, whose names suggest overlapping retrieval behavior.

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?

Usage is implied by the phrase 'for a specific topic', which tells the agent the tool is topic-scoped. However, there is no explicit when-to-use/when-not guidance and no mention of alternatives such as palim_search or palim_resume, so the agent must infer the boundary between this and its retrieval siblings.

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