Skip to main content
Glama
Sign In

CutClip.one

by one.cutclip
OverviewDiscussionsAdmin

character.add_reference

Attach an image asset (e.g. an uploaded photo via asset.upload) to a character as one view of its character map. The first reference becomes the identity anchor.

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>",
      "expectedVersion": "<expectedVersion>",
      "characterId": "<characterId>",
      "assetId": "<assetId>",
      "view": "<view>"
    },
    "name": "character.add_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes
labelNo
assetIdYes
projectIdYes
characterIdYes
makePrimaryNo
expectedVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/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 only discloses one behavior: the first reference becomes the identity anchor. It says nothing about optimistic concurrency via expectedVersion (a required parameter whose failure mode is the main way this call breaks), whether adding a reference can replace or invalidate an existing one, permission requirements, or reversibility via character.remove_reference.

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 short sentences, front-loaded with the action and resource, followed by the one non-obvious side effect. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 7-parameter mutation tool with 5 required fields, no annotations, and no output schema needs considerably more: the required version-concurrency parameter is undocumented, the enum for view is only alluded to, and no return value or error behavior is hinted at. The identity-anchor note is valuable but covers only a fraction of what an agent needs to invoke this 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 7 parameters, so the description must compensate. It adds meaning only for assetId (an image asset obtained via asset.upload) and partially for view (one view of the character map); projectId, characterId, expectedVersion, label, and makePrimary are left entirely unexplained, and makePrimary's relationship to the 'identity anchor' sentence is ambiguous.

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 and resource: 'Attach an image asset ... to a character as one view of its character map.' It also names the source tool (asset.upload) and the effect on the character map's identity anchor. It does not explicitly contrast with character.remove_reference or character.set_primary, so it falls short of full sibling differentiation.

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?

Usage is implied: the agent gathers that this is the tool for adding imagery to a character from an uploaded asset, and the asset.upload pointer gives a prerequisite step. There are no explicit when-not conditions, no mention of how to change the primary reference later, and no note on what to do when a similar view already exists.

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