Skip to main content
Glama

studio_bind_project

Links a canonical production to an account-local provider project and records uploaded reference and created character IDs for that binding.

Instructions

Link a canonical production to an account-local provider project, with IDs of uploaded references and created characters.

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>",
      "accountId": "<accountId>",
      "remoteProjectId": "<remoteProjectId>"
    },
    "name": "studio_bind_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsNo
accountIdYes
projectIdYes
charactersNo
remoteProjectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It implies a persistent linking operation but does not disclose whether rebinding overwrites an existing link, what permissions are required, whether the operation is idempotent, or what side effects occur on the remote provider.

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?

The definition is a single front-loaded sentence with no filler. It is efficient, though the density leaves important semantics unexplained rather than redundant.

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?

This is a mutation tool with nested object parameters, no annotations, no output schema, and no parameter descriptions. The one-sentence description omits prerequisites, mapping semantics, idempotency, error behavior, and result handling, which is inadequate for the tool's complexity.

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%, so the description must explain five parameters. It only hints that 'assets' are uploaded references and 'characters' are created characters; it does not explain the key/value structure of those nested objects or clarify the distinction between projectId, accountId, and remoteProjectId.

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 description states a specific verb and resource: it links a canonical production to an account-local provider project. The operation is distinguishable from import or dispatch siblings, though the jargon 'canonical production' is not defined and no sibling is explicitly contrasted.

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 guidance on when to use this tool versus studio_import_project, studio_sync_plan, or other siblings. The phrase 'uploaded references and created characters' hints at prerequisites, but no ordering, preconditions, or exclusions are stated.

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