Skip to main content
Glama

Palim

by io.github.joleschmidt

palim_get_brain

Read-onlyIdempotent

Distilled knowledge profile. No args: recent topic index (capped). With topic: full document. Pass limit for a larger or full index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax topics in the index (most recently updated first). Default 20 when omitted. Pass 0 for every topic.
topicNoOptional topic slug or name. When set, returns the full topic document instead of the index.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesHuman-readable tool result text.

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 non-destructive, so safety is covered. The description adds mode-dependent behavior (index vs full document and capped index), which is useful, but much of it is also reflected in the schema. No contradiction with 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 short sentences with no redundant words. Each sentence conveys a distinct behavior: no args, with topic, and with limit, making the most important behavioral variation easy to scan.

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?

The tool has only two optional parameters and an output schema, and the description covers the core invocation patterns and result types. It is sufficiently complete for an agent to call the tool safely and interpret the output, even though error cases like unknown topics are not mentioned.

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. The description lightly reinforces how limit and topic change the result, but it does not add meaningful meaning beyond what the schema already provides.

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 explains the resource (distilled knowledge profile), the primary outputs (recent topic index vs full topic document), and the input mode that selects each. The behavior is clear enough to distinguish the tool from siblings like palim_search or palim_get_context, though no sibling is named.

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?

It gives operational guidance for no args, a topic, and a limit, but it does not explicitly state when to choose this tool over siblings such as palim_search or palim_get_context. The intended use is implied by 'distilled knowledge profile' rather than stated.

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