Vixdeo — Tu Productor IA

Commit a version

commit

Commits the project's staged conversation draft as a new version and makes it THE CUT the production line renders (isHead: true in the answer). Re-validates coherence (the same blocking/non-blocking report the human sees); force=true overrides a blocking report; as_branch=true keeps the new version as a branch instead, in the version timeline, where it can become the cut later. Requires write. $0.

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": {
      "project_id": "<project_id>"
    },
    "name": "commit"
  }
}

Input Schema

Name	Required	Description
`force`	No	Override a blocking-coherence gate.
`as_branch`	No	Keep the commit as a navigable branch INSTEAD of making it the cut the line renders. Default false: a commit is the cut.
`project_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only cover safety hints (writes, non-idempotent, non-destructive), so the description carries the important behavioral load: it re-validates coherence with the same blocking/non-blocking report the human sees, force overrides a blocking report, and the operation requires `write` scope and is `$0`. These are substantive traits beyond what annotations provide.

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?

A single dense sentence that front-loads the core action and the resulting state, then appends the two option behaviors and cost/auth facts. No filler and each clause earns its place.

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

Completeness5/5

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

For a mutation tool with no output schema, the description covers the state transition (`isHead: true` in the answer), the gating behavior, the branch alternative, the required scope, and cost. An agent has everything needed to call it correctly.

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 67% – force and as_branch already have descriptions – but the description sharpens them with concrete semantics ('overrides a blocking report', 'keeps the new version as a branch ... where it can become the cut later'). project_id remains undocumented in both places, keeping it from a 5.

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

Purpose5/5

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

States a specific verb ('commits') and resource ('staged conversation draft as a new version') and clarifies the resulting state ('makes it THE CUT the production line renders'). The agent can distinguish this from siblings like set_head or cancel without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly signals the precondition (a staged draft) and the two behavioral modes (force to override a blocking gate, as_branch to keep it as a branch instead of the cut). It stops short of explicitly naming when to use set_head instead, so routing against siblings is implied rather than spelled out.

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

All Vixdeo — Tu Productor IA tools Inspect

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

Need Help?