Palim

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

Name	Required	Description	Default
`limit`	No	Max topics in the index (most recently updated first). Default 20 when omitted. Pass 0 for every topic.
`topic`	No	Optional topic slug or name. When set, returns the full topic document instead of the index.

Output Schema

Name	Required	Description	Default
`message`	Yes	Human-readable tool result text.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 29, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Max topics in the index (most recently updated first). Default 20 when omitted. Pass 0 for every topic.",
+  "type": "number"
+}

Changed1 schema field changedAug 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "description": "Human-readable tool result text.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "message"
+  ],
+  "type": "object"
+}

First observedAug 6, 2026

TDQS

A3.5/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 index is capped by default and can be expanded, which is modest extra context, but it says nothing about size limits, rate behavior, or what 'distilled' implies about completeness.

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?

Three short clauses, front-loaded with the resource and mode behavior; nothing is padded. The telegraphic fragment style is efficient but slightly terse for an agent parsing mode semantics.

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, return-value detail is not required, and the description covers both call shapes adequately. The remaining gap is the absence of any guidance on choosing this over palim_get_context or 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 the schema already documents both parameters fully, including defaults and the 0-for-everything case. The description's 'Pass limit for a larger or full index' merely restates schema content, so the baseline 3 applies.

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+resource ('Distilled knowledge profile') and describes both operating modes: no args returns a topic index, with topic returns the full document. However, 'brain' is internal jargon and the description never distinguishes this from sibling tools like palim_get_context or palim_search, which an agent must choose between.

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 clearly explains the two modes and what the limit parameter changes, which is useful conditional guidance. But it gives no when-to-use context relative to siblings such as palim_get_context, palim_search, or palim_resume, so routing remains an inference.

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

All Palim tools Inspect

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.