Music360 MCP

music360_list_show_roteiro

Lista o roteiro e logística do show em ordem: ref, tipo, título, status, início, fim, origem, destino, detalhes, passageiros e, nos eventos, as etapas com horário. Mostra também se o roteiro está bloqueado. Exige "Visualizar roteiro de show".

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": {
      "show_id": "<show_id>"
    },
    "name": "music360_list_show_roteiro"
  }
}

Input Schema

Name	Required	Description
`show_id`	Yes	public_uid do show (ex.: A0001-SHW-00001F).
`response_profile`	No	Perfil de resposta. Listagens usam summary por padrão; sensitive exige admin.
`sensitive_access_purpose`	No	Finalidade operacional obrigatória quando response_profile=sensitive ou include_sensitive_details=true.
`include_sensitive_details`	No	Retorna detalhes sensíveis mínimos quando autorizado por escopo admin. Padrão: false.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the burden: it discloses the permission requirement, the fixed field ordering, and that blocked status is reported. It does not cover pagination, ordering semantics beyond field order, or what sensitive profiles return, which the schema only partially handles.

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?

Front-loaded with the action and resource, then the field list and the permission clause. The field enumeration is long but functional since there is no output schema; little is wasted.

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?

No output schema exists, so the description compensates by enumerating returned fields and noting the blocked flag and event-step times, plus the authorization requirement. For a read-only listing of this complexity it covers what an agent needs.

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?

Schema description coverage is 100%, so all four parameters (including the response_profile enum and sensitive_access_purpose) are already documented. The description adds nothing parameter-specific beyond the show context.

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?

States a specific verb ('Lista') and resource ('roteiro e logística do show'), then enumerates the returned fields and adds the blocked-status flag. It is clearly distinct from music360_get_show or music360_list_show_musicas, though no sibling is named explicitly.

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 the resource and the stated permission prerequisite ('Exige Visualizar roteiro de show'), but there is no explicit guidance on when to pick this over music360_get_show or music360_list_show_equipe, and no exclusions.

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

All Music360 MCP 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?