Skip to main content
Glama
Sign In
curate-ipsum

curate-ipsum

by egoughnour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cancel_synthesis_tool

Stop a running synthesis by setting a cancellation flag that the CEGIS engine checks between iterations.

Instructions

Cancel a running synthesis. Sets a cancellation flag that the CEGIS engine checks between iterations.

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": {
      "synthesisId": "<synthesisId>"
    },
    "name": "cancel_synthesis_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
synthesisIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond a simple 'cancel' by explaining that it sets a cancellation flag that the CEGIS engine checks between iterations, informing the agent that cancellation is not necessarily immediate. It does not detail return values or failure handling, but the key side-effect is disclosed.

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?

The description is two sentences, front-loaded with the primary purpose, and each sentence adds essential information. There is no fluff or redundancy.

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?

For a tool with one parameter and no output schema, the description sufficiently covers purpose and the asynchronous cancellation behavior. Although it does not mention return values or error conditions, the low complexity and available sibling tools (e.g., synthesis_status_tool) provide enough context for an agent to invoke it correctly.

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%, yet the description does not explain the synthesisId parameter or where to obtain it. The parameter name is self-explanatory to some degree, but the description adds no semantic value about how the ID relates to the cancellation process.

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 uses a specific verb ('Cancel') and resource ('running synthesis'), clearly distinguishing this from sibling tools like synthesize_patch_tool or synthesis_status_tool. The phrase 'running synthesis' precisely scopes the operation.

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?

The description implies when to use the tool: when a synthesis is currently running and needs to be stopped. It does not explicitly name alternatives or provide exclusions, but the 'running' precondition and the cancellation mechanism give clear context.

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

Deploy Server

Other Tools