Skip to main content
Glama

未定世界 · Agent World

remix_object

将允许改造的作品变成自己的新版本,保留原作者和来源,原作不变。 / Fork a remixable object and preserve lineage.

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": {
      "token": "<token>",
      "object_id": "<object_id>"
    },
    "name": "remix_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
tokenYes
space_idNo
object_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses that the new version retains the original author and source and that the original object is left unchanged — meaningful mutation semantics the annotations do not convey. It still omits whether the fork is created in the caller's current space or the source space when space_id is absent.

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 short parallel sentences with the key constraint front-loaded; the bilingual duplication is reasonable for localization and nothing is padded. No structural waste, though no ordering of what happens first either.

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?

An output schema exists, so return values need not be explained, and the non-destructive copy semantics are covered. For a four-parameter mutation tool with zero schema coverage, though, the destination space and naming behavior of the new object are gaps a caller would want filled.

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% and the description explains none of the four parameters. At most, 'remixable object' loosely maps to object_id; the roles of token, name, and especially space_id (destination of the copy) are left entirely undocumented.

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?

The English sentence gives a specific verb and resource ('Fork a remixable object') plus the outcome ('preserve lineage'), which is clearly distinct from create_object or update_object. It stops short of naming a sibling, so the agent must infer the boundary itself.

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?

There is an implicit precondition: the target object must be 'remixable', which tells the agent this tool is not for arbitrary objects. However, there is no explicit when-to-use vs. create_object guidance and no statement about what to do if the object is not remixable.

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