Skip to main content
Glama
Sign In
3D Texel MCP server

3D Texel MCP server

by Gatyh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Cancel a generation

cancel_generation
Destructive

Stop a running generation and automatically refund its credits. Use when an AI agent needs to halt an active 3D Texel job by providing a generation ID.

Instructions

Cancel a running generation; its credits are refunded.

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": {
      "generation_id": "<generation_id>"
    },
    "name": "cancel_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
generation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, destructive operation. The description adds genuine behavioral value beyond them: cancelling is non-destructive to the user's credits because 'its credits are refunded', which tells the agent the cost impact of the action.

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?

A single sentence with the action front-loaded and the refund consequence attached via a semicolon. Nothing wasted, nothing missing.

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 one-parameter cancel operation, the description plus destructive annotations cover the essentials, and the refund note closes the main cost uncertainty. The only gap is the lack of any statement about what the call returns or confirming the post-state of the generation.

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

Parameters3/5

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

One required parameter with 0% schema description coverage, so the schema explains nothing about generation_id. The description only implies it identifies the 'running generation'; it adds no format, source, or constraints beyond that implication.

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?

States a specific verb and resource ('Cancel a running generation') with no ambiguity, and 'running' scopes which generations are eligible. No sibling offers cancellation, so the agent can distinguish it immediately from the generate_*/get_*/list_* family.

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?

The word 'running' implies the tool applies only to in-progress generations, which is implied usage guidance. However, there is no explicit statement of when not to use it (e.g. already-finished or failed generations) and no named alternative.

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