Skip to main content
Glama

mcp_engram_goal_create

Create a goal block to declare agent intent, geometrically bound to the ego, influencing future recall and continuity via goal stack.

Instructions

Create a new goal block as part of the agent's explicit goal stack. This is the primary entry point for declaring intent that should be geometrically bound to the ego and influence future recall and continuity. Goals created here can be linked to traces via goal_context and will be surfaced by the engram-goal skill and ki_hijacker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
affirmNoCore positive claim/intent being advanced by this goal (A/D/R triad for goal decomp; optional)
denyNoRisks or alternatives being rejected for this goal (A/D/R; optional)
goal_idNoOptional stable concept name (e.g. engram_mvp_v1 → goal:engram_mvp_v1). If omitted, a timestamped goal:* key is minted.
parentNoParent goal concept name (for decomposition, optional)
priorityNohigh | medium | low (default: medium)
reconcileNoSynthesis/fruit: how this goal resolves tensions or advances coherence (A/D/R 'fruit' carrier; optional)
statementYesClear, single-sentence description of the goal
Behavior2/5

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

No annotations are provided, so the description bears full burden. It mentions goals being surfaced by engram-goal skill and ki_hijacker, but does not disclose side effects, permissions, or safety considerations for a creation tool.

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?

Two sentences, front-loaded with key purpose, no wasted words.

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 7 parameters and no output schema, the description covers the creation intent and linking behavior but lacks return value info or examples. Adequate but with gaps.

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 coverage is 100% with parameter descriptions. The tool description adds context about A/D/R triad and linking to traces, but does not elaborate beyond schema. 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 clearly states 'Create a new goal block as part of the agent's explicit goal stack' and distinguishes it from sibling goal tools (e.g., goal_decompose, goal_list) by emphasizing creation and linking to traces.

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 says 'primary entry point for declaring intent' and mentions linking to traces, but does not explicitly state when to avoid this tool or provide alternatives among the many sibling goal tools.

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/staticroostermedia-arch/engram'

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