Skip to main content
Glama

twining_record

Record session summaries, decisions with rationale, and findings. Call before committing or ending a session to persist choices and discoveries for future agents.

Instructions

Record what you did, any choices you made, and anything you discovered. Call before committing or ending a session. The summary becomes a status post. Decisions become tracked records with rationale. Findings become blackboard entries visible to future agents. Scope is auto-inferred from git diff if omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesWhat you did this session — one or two sentences
decisionsNoChoices you made. Each item is either a natural-language sentence ("Chose X over Y — reason") or a structured object ({ summary, rationale, alternatives: [{ option, reason_rejected }] }) when the content is too long or too structured for the NL parser to split cleanly.
findingsNoDiscoveries, warnings, or needs. Prefix with "warning:" or "need:" for severity. E.g. ["Auth tokens stored in localStorage — fails SOC2", "warning: No token rotation exists", "need: Add rate limiting before launch"]
assumptionsNoConditions your decisions depend on. E.g. ["Data is relational", "No strict ordering required"]
constraintsNoWhat limited your options. E.g. ["Must support Node 18+", "Cannot add new dependencies"]
affected_filesNoFile paths you changed or that are affected by your decisions
affected_symbolsNoFunction/class/method names affected by your decisions
depends_onNoIDs of prior decisions that your decisions depend on (from twining_assemble or twining_why output)
supersedesNoID of a prior decision that your work replaces or invalidates
reversibleNoWhether your decisions are easily reversible (default: true)
commit_hashNoGit commit hash to associate with these decisions
scopeNoArea of codebase affected. Auto-inferred from git diff if omitted.
agent_idNoAgent identifier (default: main)
Behavior4/5

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

Discloses side effects: summary becomes a status post, decisions become tracked records, findings become blackboard entries visible to future agents. Also mentions auto-inference of scope from git diff. No annotations present, so description carries full burden; it covers key behaviors well.

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?

Five sentences with no redundancy. The main purpose is front-loaded, and each sentence adds critical context. Efficient and well-structured.

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?

The description explains the overall behavior and side effects adequately. With 13 parameters mostly documented in schema, the description fills in the high-level workflow. No output schema, but description covers return side effects. Slight lack of detail on parameter interactions, but sufficient for an agent.

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%, so baseline is 3. Description does not add parameter-specific details beyond what the schema already provides. The auto-inference of scope is already in schema. No extra value added.

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 records actions, choices, and discoveries. It specifies when to call ('before committing or ending a session') and distinguishes itself from siblings by describing the outputs (status post, tracked decisions, blackboard entries).

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?

Provides explicit timing for use ('call before committing or ending a session') but does not mention when to use alternative tools like twining_assemble or twining_why. Context is clear but exclusions are missing.

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/daveangulo/twining-mcp'

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