Skip to main content
Glama
marerem

longmem

by marerem

confirm_solution

Auto-save a working solution with context from your last similar search. Just provide the solution text; problem metadata is filled automatically.

Instructions

Auto-save a confirmed solution using context from the last search_similar call.

Call this after solving a problem instead of save_solution — you only need to provide the solution text. Problem description, category, tags, and language are taken automatically from the last search_similar call.

If save_solution was already called manually this session, this is a no-op (no duplicate will be created).

Input Schema

NameRequiredDescriptionDefault
solutionYesThe solution that worked. Include code, commands, or steps. Problem metadata (category, tags, language) are filled in automatically from the last search_similar call.
projectNoRepository or workspace name this was solved in.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.7/5.0
Behavior4/5

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

Discloses auto-filling of problem metadata and no-op behavior, but lacks details on failure modes or side effects beyond annotations.

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 concise paragraphs front-load key information with no wasted words.

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

Completeness5/5

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

Covers all essential aspects: purpose, when to use, auto-fill behavior, duplicate prevention, and parameter meanings.

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?

Schema has full coverage; description adds context about auto-fill and no-op, enhancing understanding of the 'solution' and 'project' parameters.

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 auto-saves a confirmed solution using context from the last search_similar call and distinguishes itself from save_solution.

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

Usage Guidelines5/5

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

Explicitly says to call after solving a problem instead of save_solution, and mentions no-op behavior if save_solution was already called.

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