Turbo Quant Memory MCP Server

by Lexus2016

Overview Schema Source Related Servers Discussions Admin

announce_work

Announce planned code changes to other agents in a working tree, then see peers whose declared areas overlap and recent changes in those areas to avoid conflicts.

Instructions

Tell the other agents in this working tree what you are changing.

feature: short name of the work. areas: workspace-relative files or directories (globs allowed). Returns the peers whose announced areas overlap yours and recent changes inside them. Inferred writers are guesses from announced areas, never facts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feature": "<feature>"
    },
    "name": "announce_work"
  }
}

Input Schema

Name	Required	Description	Default
`areas`	No
`details`	No
`feature`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.36.1Nov 10, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says what is returned and warns that inferred writers are guesses, but it does not explain persistence, visibility to other agents, whether announcements are replaced or accumulated, or lifecycle relationship to finish_work.

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?

The description is short, front-loaded, and free of filler. The inline parameter notes are serviceable, though a clearer parameter-by-parameter structure would improve scanability.

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?

An output schema exists, so the return-value explanation is not strictly required, but the description usefully adds the overlap and recent-changes behavior plus a reliability caveat. However, for a tool with no annotations and 0% schema description coverage, the missing details parameter and lifecycle guidance leave important gaps.

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?

Schema description coverage is 0%, so the description must compensate. It explains feature as a short name and areas as workspace-relative files or directories with glob support, but it completely omits the optional details parameter.

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 states a specific action and resource: telling other agents in the working tree what you are changing. It clearly establishes the scope as the current working tree, but does not distinguish this from the likely sibling finish_work.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, nor when not to use it. The purpose implies it is used when starting or changing work, but the description does not state prerequisites or mention finish_work.

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