Skip to main content
Glama

Discard Style Sheet

lab_stilblatt_verwerfen

Discard the style sheet, so runs in this project use the neutral sheet again. A new sheet costs credits again, so confirm with the person first.

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": {
      "project_id": "<project_id>",
      "character_id": "<character_id>"
    },
    "name": "lab_stilblatt_verwerfen"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject id, positive integer as string
character_idYesCharacter id from lab_list_characters, positive integer as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write nature is known. The description adds real value by disclosing the credit cost of regeneration and the human-confirmation requirement. It does not say whether the discarded sheet is deleted or merely unassigned, nor whether the state is reversible — the only residual ambiguity, which keeps it at 3 rather than higher.

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 tight sentences: outcome first, cost/confirmation warning second. No redundant restatement of the title or schema, and every clause carries information.

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 2-parameter mutation with full schema coverage, an annotation set and no output schema, the description covers purpose, effect and caution well. The only gap is the fate of the existing sheet (deleted vs. unassigned) and its reversibility.

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?

Schema description coverage is 100% and both parameters are documented in the schema, including the pointer to lab_list_characters for character_id. The description adds nothing about parameters, which is acceptable given the schema baseline of 3.

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 ('Discard') and resource ('the style sheet'), plus the observable effect on the project ('runs ... use the neutral sheet again'). That effect implicitly separates it from the sibling creation/approval tools (lab_stilblatt_erzeugen, lab_stilblatt_freigeben), though no sibling is named explicitly.

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?

Gives clear conditional guidance: confirm with the person first, because regenerating costs credits. It does not name alternatives or spell out when-not to call it (e.g. if no sheet is assigned), so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources