Turbo Quant Memory MCP Server

by Lexus2016

Overview Schema Source Related Servers Discussions Admin

Python

Local

finish_work

Clears work announced for the current session to mark it complete and remove it from active session tracking.

Instructions

Clear the work this session announced with announce_work.

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": "finish_work"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.36.1Nov 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Clear' signals removal or reset of session-scoped work state, but the description does not say whether the removal is permanent, whether it is idempotent if nothing was announced, or whether it affects anything outside the current session.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence that front-loads the action and names its counterpart tool, with no filler. It is terse to the point of underspecification about the effect of 'clear', but nothing is wasted.

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?

For a zero-parameter tool with an output schema and no annotations, the description supplies the essential pairing with announce_work. It leaves the semantics of 'clear' (durability, idempotency, scope of effect) unstated, which is the main remaining gap.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-level meaning is missing.

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?

States a specific verb ('Clear') against a specific resource ('the work this session announced'), and ties it explicitly to the sibling announce_work, so the pairing is unambiguous. It stops short of saying what 'clearing' actually does to that state, which keeps it from 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 Guidelines3/5

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

Naming announce_work implies the intended sequence: announce work, then call this to clear it. There is no explicit statement of when this should be called (end of session? after every task?) nor any condition under which it should not be used, so the guidance is only implied.

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