Skip to main content
Glama

Change a kit piece

update_kit_piece
Idempotent

Rename it, change its handle or description, crop it again, or share it crop is cut again from the image the piece was added from. kept true keeps another angle of a place that is pending (a brief can mention it then). shared: offer it (a character too) to every other artist's songs (true), or keep it to its own artist's (false); it stays in its own artist's kit either way. ai_made, on a character only: an AI-made person who looks like no real person (true), or a real one (false); a person who passed a face check is real (withdraw it first). Plans already made keep the pieces as they were planned.

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": {
      "kit_id": "<kit_id>"
    },
    "name": "update_kit_piece"
  }
}

Input Schema

NameRequiredDescriptionDefault
cropNoThe new rectangle, in fractions of the source image
keptNoAnother angle of a place that is pending (draw_place_angles): keep it in the kit. To leave it out, delete it
nameNo
handleNo
kit_idYesThe kit piece id
sharedNoOffer it to every other artist’s songs too (true), or only its own artist’s (false)
ai_madeNoA character only: an AI-made person (true) or a real one (false)
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / kept
      Added value: +{
      +  "const": true,
      +  "description": "Another angle of a place that is pending (draw_place_angles): keep it in the kit. To leave it out, delete it",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / shared
      Added value: +{
      +  "description": "Offer it to every other artist’s songs too (true), or only its own artist’s (false)",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / ai_made
      Added value: +{
      +  "description": "A character only: an AI-made person (true) or a real one (false)",
      +  "type": "boolean"
      +}
  4. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare a non-destructive, idempotent write, and the description adds genuinely non-obvious behavior on top: `kept: true` retains a pending angle of a place so a brief can reference it, `shared` does not remove the piece from its own artist's kit, `ai_made` cannot be flipped to false while a face-check has passed (must be withdrawn first), and "Plans already made keep the pieces as they were planned" discloses that updates do not retroactively alter existing plans. These are meaningful side-effect and constraint disclosures that annotations alone could not convey.

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

Conciseness2/5

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

Everything is packed into one run-on paragraph with dangling clauses and an apparent word-drop that merges the crop and share explanations. The information is valuable but not front-loaded or segmented by parameter, forcing the reader to untangle it.

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 an eight-parameter mutation with a nested crop object and no output schema, the description covers the subtle semantics well (kept, shared, ai_made, plan immutability) but omits framing such as required permissions, what happens to unspecified fields, and the meaning of kit_id versus the other identifiers. Adequate, not complete.

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?

Schema coverage is 63%, and the prose supplies the missing meaning for the tricky parameters: kept, shared, ai_made, and crop (re-cut from the original source image, not from the current crop). It does not elaborate on name/handle/description formatting, but those are self-evident from the schema constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening enumerates concrete updatable fields (rename, handle, description, crop, share), so the resource and operation are identifiable. However, the sentence collapses mid-way ("or share it crop is cut again from the image the piece was added from"), fusing the crop note into the share clause, which makes the scope of the tool harder to read at a glance than it should be.

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 statement of when to use this versus add_kit_piece, delete_kit_piece, or get_kit_piece. The only routing hint is buried inside the schema for `kept` ("To leave it out, delete it"), and the description itself offers no exclusions or prerequisites.

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