Show an overview of all available Palim tools and usage instructions.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Filter by category. Default: all. |
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | Human-readable tool result text. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "message": {
+ "description": "Human-readable tool result text.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "message"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing this as a safe, read-only help operation. The description adds no extra behavioral context beyond restating the purpose, so it adds limited value beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that delivers the essential purpose without any filler or redundant phrasing. It is front-loaded and earns its place with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple help tool with one optional parameter, a complete schema, and rich annotations, the description is sufficiently complete. It explains the tool's purpose and output (overview and instructions), and the output schema (present) can provide any return-value details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers 100% of the parameter (category) with a clear enum and description, so the description does not need to add parameter details. The description doesn't mention the category parameter, but the schema fully handles it, placing this at the baseline for high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Show') and resource ('all available Palim tools and usage instructions'), making the tool's purpose immediately clear. It is distinct from sibling tools, which perform operations on data rather than providing help.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies this tool is for getting an overview and usage instructions, which is the right context for a help command. It doesn't explicitly name alternatives or exclusions, but given its unique role among the sibling tools, the usage context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.