Tasvr

Everything for one festival or performance scene

get_scene_bundle

Read-only

For a festival or folk-dance scene: roles (poses), wardrobe that fits each role's gender, group formations and environments, as one capped shortlist. Nothing is chosen.

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": {
      "tradition": "<tradition>"
    },
    "name": "get_scene_bundle"
  }
}

Input Schema

Name	Required	Description	Default
`tradition`	Yes	e.g. "bihu", "garba", "bhangra", "thiruvathira", "ghoomar", "lavani", "dandiya-raas".
`peopleCount`	No	Total people in the shot. Filters formations to those that need no more than this.

Output Schema

Name	Required	Description	Default
`error`	No
`label`	No
`roles`	No
`available`	No
`tradition`	No
`formations`	No
`environments`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations establish read-only and closed-world behavior. The description adds useful behavioral context: results are a 'capped shortlist' and 'Nothing is chosen,' so the agent knows it receives candidates rather than a final selection and that output volume is limited. It does not discuss pagination or rate limits, but the output schema covers return structure.

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?

Single front-loaded sentence with a compact colon list; no filler. Slight ambiguity from a missing verb and the terse phrase 'Nothing is chosen' keeps it from a 5.

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?

For a two-parameter read-only bundle tool with an output schema and clear annotations, the description covers what the bundle contains and its shortlist nature. It is only missing sibling routing guidance, which prevents a 5.

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?

With 100% schema coverage, the schema documents tradition and peopleCount, including examples and the 1-25 cap. The description does not add parameter-specific meaning beyond implying tradition scoping and formation filtering, so baseline 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 identifies the resource as a scene bundle and enumerates its components (roles, wardrobe, formations, environments) for festival/folk-dance contexts. It lacks an explicit verb and does not name sibling list tools to distinguish it, but the 'one capped shortlist' framing makes the aggregation role clear.

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 by 'For a festival or folk-dance scene,' suggesting this is the one-stop lookup when assembling a scene. There is no explicit when-to-use/when-not guidance or reference to alternatives such as list_scene_traditions or the individual list tools.

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

All Tasvr 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?