Skip to main content
Glama

Get a casting

get_music_video_casting
Read-onlyIdempotent

A casting's people as proposed, then as drawn status: proposed (not drawn), drawing (their sheets are drawn: check back in about a minute), ready or failed. Each person: index, name, role, does, description, shots, state (proposed, declined, drawing, kept: drawn and in the song artist's kit; chosen: a kit character in that role; failed, with error) and character once kept or chosen. price.per_person is a sheet's price; charged is what was spent. people_for_brief, once ready: the {character, does} entries to add to people in plan_music_video, design_music_video_shoot and create_music_video.

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": {
      "casting_id": "<casting_id>"
    },
    "name": "get_music_video_casting"
  }
}

Input Schema

NameRequiredDescriptionDefault
casting_idYesThe casting id (casting_…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already establish it is a safe, idempotent read, and the description adds substantial behavior beyond them: a state machine (proposed, drawing, ready, failed), an expected wait of roughly a minute for drawing, the fact that people_for_brief only exists once ready, and the meaning of price.per_person versus charged. That is exactly the kind of context an agent needs to call and interpret this correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

No filler sentences, but the phrasing is dense and occasionally hard to parse: 'as proposed, then as drawn status' and the parenthetical state definitions pack multiple ideas into single clauses. The per-person field list is valuable but would read better as a structured enumeration; front-loading the core purpose before the field dump would help.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so well: person fields, state meanings, pricing semantics, and the conditional people_for_brief. It is slightly incomplete about top-level structure and error/not-found behavior, but an agent has enough to call and interpret the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter, casting_id, and the schema documents it fully at 100% coverage with its pattern. The description adds nothing about the id beyond what the schema already says, so the baseline of 3 applies.

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 makes clear this returns a casting's people and their draw state, with per-person fields and pricing. It does not lead with an explicit 'retrieves the casting with this id' verb+resource statement, but 'A casting's people as proposed, then as drawn' plus the readiness/people_for_brief notes make the resource and scope unmistakable. Sibling differentiation (vs. draw_music_video_cast or cast_music_video) is only implicit.

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 rather than stated: poll again 'in about a minute' while drawing, and once ready use people_for_brief in plan_music_video, design_music_video_shoot and create_music_video. That is genuinely useful downstream routing, but there is no explicit statement of when to call this instead of draw_music_video_cast or cast_music_video, and no guidance on calling it before casting.

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