Skip to main content
Glama
Sign In

CutClip.one

by one.cutclip
OverviewDiscussionsAdmin

character.generate_view

Generate (or regenerate) one view of a character's map, e.g. an expression. Costs credits, charged to the project owner.

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": {
      "projectId": "<projectId>",
      "characterId": "<characterId>",
      "view": "<view>"
    },
    "name": "character.generate_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes
labelNo
projectIdYes
imageModelNo
characterIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral trait: the call costs credits charged to the project owner. It does not say whether generation is synchronous or asynchronous, whether an existing view is overwritten, or what permissions are required — all material for a paid mutation.

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?

Two sentences with no filler, and the cost warning is placed where it will be read before invoking. The only inefficiency is the vague term "map", which spends a word without adding precision.

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 a credit-consuming generation tool with no annotations, no output schema, and 0% parameter documentation, the description covers cost but leaves the post-call lifecycle (job handling, overwrite behavior, model selection) unstated. Adequate to invoke, thin for invoking 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% across 5 parameters, so the description must compensate. It only sheds light on "view" (example: an expression) and indirectly on projectId via "charged to the project owner"; label, imageModel, and characterId get no meaning, and imageModel in particular is opaque without guidance.

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?

"Generate (or regenerate) one view of a character's map" gives a specific verb and a scoped resource; "one view" implicitly contrasts with the sibling character.generate_sheet, which produces a whole sheet. The word "map" is unexplained and only becomes concrete via the view enum, so it stops short of a 5.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named (character.generate_sheet is the obvious fork point). The parenthetical "(or regenerate)" hints that re-running over an existing view is allowed but does not state the effect on the prior image.

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

All CutClip.one toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources