Skip to main content
Glama

Save reflection answers

save_reflection

Captures a person's answers to Phase 1 reflection questions as they respond, updating only answered fields in their own lightly tidied words so existing responses stay intact.

Instructions

Save answers to Phase 1 questions as the person gives them. Only include the fields answered; others are kept. Use the person's own words, lightly tidied.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_reflection"
  }
}

Input Schema

NameRequiredDescriptionDefault
hardNo
nameNo
proudNo
gentleNoWhat needs gentleness this year; empty string if nothing
visionNo
decisionNoA decision they are waiting on; empty string if none
gratefulNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose an important trait: this is a partial merge, not a replacement — unanswered fields are preserved. It does not say whether repeated calls overwrite prior answers, what the response looks like, or whether any confirmation/permission step is involved, leaving real gaps for a write 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?

Three short sentences, front-loaded with the action, then the partial-merge rule, then the phrasing constraint. Every sentence carries operational information and nothing is padded.

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 seven optional free-text parameters, no annotations, and no output schema, the description covers invocation style and merge behavior but leaves the meaning of five of seven fields undocumented. An agent could call it, but would be guessing at what to put in 'hard', 'proud', 'vision', and 'grateful'.

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

Parameters2/5

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

Seven parameters with only 29% schema coverage, and the description adds almost no per-field meaning beyond 'use the person's own words' (implying free-text). Terse names like 'hard', 'proud', and 'gentle' are opaque without the Phase 1 question text, which the description never supplies. The partial-update sentence implies all fields are optional but does not explain what each captures.

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

Purpose4/5

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

The description names a specific verb and resource — saving answers to 'Phase 1 questions' — which is concrete enough to separate it from siblings like save_baseline or save_values, whose domains differ. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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?

'Save answers ... as the person gives them' establishes when to call it (incrementally, during conversation), and 'Only include the fields answered; others are kept' tells the agent how to call it for partial data. There are no explicit exclusions or named alternatives, which keeps it out of 5 territory.

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