Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

Start approved studio task

start_studio_task
DestructiveIdempotent

Admit exactly the server-approved studio proposal once. All native descendants retain the actor, owner, payer, limits and source authority. No implicit publication, recurrence, purchases or auto-reload.

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": {
      "proposal_id": "<proposal_id>",
      "request_key": "<request_key>"
    },
    "name": "start_studio_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
proposal_idYes
request_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Beyond annotations, it discloses that descendants retain actor, owner, payer, limits, and source authority, and that publication, recurrence, purchases, and auto-reload are not implicitly triggered. That is meaningful behavioral context, though it still does not explain what destructive effect is performed despite destructiveHint=true.

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 description is short and front-loads the action, with no wasted framing. Its only weakness is that dense jargon such as 'native descendants' reduces immediate comprehension.

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?

Annotations cover the safety profile and an output schema exists, so return values need not be described. Still, for a two-parameter destructive, open-world operation with 0% schema coverage, the description leaves parameter meanings and the relationship to prepare_studio_task under-specified.

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 never names proposal_id or request_key. 'Server-approved studio proposal' gives some implicit meaning to proposal_id, and 'exactly once' hints at request_key's idempotency role, but neither parameter is adequately defined.

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

Purpose3/5

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

The description says to 'Admit exactly the server-approved studio proposal once,' which narrows the action to committing an approved proposal rather than preparing one. However, 'admit' is nonstandard and the description never plainly says it starts a studio task, leaving the core purpose somewhat opaque.

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?

It implies the proposal must already be server-approved and can be admitted only once, but there is no explicit when-to-use guidance and no mention of prepare_studio_task or other alternatives. The agent must infer that this is the execution step following preparation.

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

All GenFlick 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