Skip to main content
Glama
phasespace-labs

palinode

by phasespace-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

palinode_trigger

Create, list, or delete semantic triggers that automatically inject a specified memory file when a future user message matches the described context.

Instructions

Register or manage a prospective trigger for Palinode. When a future user message semantically matches the description, the specified memory file will be automatically injected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'create', 'list', or 'delete'create
authorityNoFor 'create': who or what licensed this trigger to act — a user grant, a session id, a policy name. Stored and shown, not enforced.
thresholdNoFor 'create': Similarity threshold (0.0–1.0). Higher = stricter match required to fire. Default 0.75.
expires_atNoFor 'create': ISO-8601 timestamp after which the trigger no longer fires (it stays listed, disabled). Omit for no expiry.
trigger_idNoFor 'delete' or 'create': Custom UUID or ID to delete/create
descriptionNoFor 'create': What context should fire this trigger (e.g., 'User is discussing deployment')
memory_fileNoFor 'create': Relative path to the memory file to inject when fired (e.g., 'projects/my-app.md')
cooldown_hoursNoFor 'create': Hours to wait between consecutive firings of the same trigger. Default 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.0
    • addedInput schema / properties / authority
      Added value: +{
+  "description": "For 'create': who or what licensed this trigger to act — a user grant, a session id, a policy name. Stored and shown, not enforced.",
+  "type": "string"
+}
    • addedInput schema / properties / expires_at
      Added value: +{
+  "description": "For 'create': ISO-8601 timestamp after which the trigger no longer fires (it stays listed, disabled). Omit for no expiry.",
+  "type": "string"
+}
  2. First observedv0.9.5

TDQS

A4/5.0
Behavior4/5

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

The description adds useful behavior beyond annotations by explaining the automatic injection mechanism and semantic matching. Annotations already indicate a mutating tool, so the added value is the 'future user message' trigger behavior. It does not elaborate on the delete action's permanence, but the schema's 'delete' enum makes that discoverable.

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 two sentences, front-loads the main purpose, and has no filler or repetition. It explains the core mechanism efficiently without duplicating the schema.

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?

Given the rich input schema and the high-level nature of the tool, the description gives enough context for an agent to understand what a trigger is and how it behaves. It does not describe return values or list/delete semantics in detail, but with no output schema and a clear action enum, this is not a critical gap.

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 all eight parameters thoroughly. The description only adds general context about semantic matching and memory injection, but does not add parameter-specific meaning beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Register or manage a prospective trigger') and clearly explains the resource and behavior: a future user message semantically matching the description causes a memory file to be injected. This distinguishes palinode_trigger from the long list of sibling tools because 'trigger' is a unique and well-defined resource in the set.

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 usage context is implied: use this tool when you want automatic memory injection based on semantic matching of future user messages. However, it does not explicitly say when not to use it or name alternatives such as manually reading or ingesting memory files, so guidance is present but not fully explicit.

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

Deploy Server

Other Tools