Skip to main content
Glama

record_entry

Record decisions, constraints, or pipelines to build durable project memory with validated required fields.

Instructions

Unified write tool: record a decision, constraint, or pipeline. Required fields by kind (validated server-side): decision needs summary/problem/why_chosen; constraint needs rule/reason; pipeline needs name/purpose/steps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesWhich kind of entry to record.
nameNopipeline: name.
ruleNoconstraint: the rule, imperative.
tagsNotags for retrieval.
scopeNoconstraint: 'global' or a file/module path.global
stepsNopipeline: ordered steps.
originNowho authored this (default agent).
reasonNoconstraint: why it exists. Min 40 chars.
problemNodecision: what forced it. Min 40 chars.
purposeNopipeline: why it exists. Min 40 chars.
summaryNodecision: what was decided (1-2 sentences).
hardnessNoconstraint: absolute vs advisory.absolute
tradeoffsNodecision: what was given up. Encouraged.
related_toNoids of related entries; get_context traverses these.
supersedesNodecision: ids of prior decisions this replaces.
why_chosenNodecision: the reasoning. Min 60 chars.
constraintsNopipeline: rules that apply.
enforced_byNoconstraint: test/command that checks it (named, never run).
project_dirNoAbsolute path to the target project. Creates .context/ if needed.
alternativesNodecision: options considered and why rejected.
what_we_triedNodecision: prior attempts. Encouraged.
when_to_invokeNopipeline: triggers. Encouraged.
retrieval_hintsNo2-4 alternate phrasings for retrieval.
constraints_createdNodecision: new constraints this introduces.
triggering_incidentNoconstraint: the incident behind it.
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It identifies the tool as a write operation and mentions server-side validation, but lacks information on side effects (e.g., creating directories), authorization needs, or return values.

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 long, front-loading the core purpose and following with essential grouping information. Every sentence is informative without superfluous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 25 parameters and no output schema, the description adequately covers required fields per kind but omits return value specification and side effects like the project_dir parameter's effect. It is sufficient for basic usage but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3. The description adds value by grouping parameters by kind and indicating required fields, which is not present in the schema's individual descriptions.

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 clearly states the tool's purpose as a unified write tool for recording decisions, constraints, or pipelines, differentiating it from sibling tools like query_entries or update_entry which handle reading or updating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool and specifies required fields per kind, but does not explicitly exclude scenarios or mention alternatives like update_entry for modifications.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jarmstrong158/context-keeper'

If you have feedback or need assistance with the MCP directory API, please join our Discord server