Skip to main content
Glama

music360_list_show_musicas

Busca músicas do catálogo dos artistas do show para montar o setlist (devolve o public_uid do fonograma e a duração).

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_musicas"
  }
}

Input Schema

NameRequiredDescriptionDefault
buscaNoParte do título ou ISRC.
limitNo
show_idYespublic_uid do show (ex.: A0001-SHW-00001F).
response_profileNoPerfil de resposta. Listagens usam summary por padrão; sensitive exige admin.
sensitive_access_purposeNoFinalidade operacional obrigatória quando response_profile=sensitive ou include_sensitive_details=true.
include_sensitive_detailsNoRetorna detalhes sensíveis mínimos quando autorizado por escopo admin. Padrão: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It usefully discloses the return shape (public_uid do fonograma e a duração) and that results are scoped to the show's artists, but says nothing about pagination/limit behavior or how the sensitive profiles affect what is returned.

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?

A single front-loaded sentence with the purpose first and the return values in parentheses; no filler. It could earn a 5 only by also carving out its relation to the setlist-fetching sibling.

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?

For a 6-parameter tool with no annotations and no output schema, the description partially compensates by naming the return fields, but leaves the sensitive/response_profile path and result-size behavior unexplained. It is adequate for the happy path only.

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 coverage is 83%, so the schema already defines busca, limit, response_profile, sensitive_access_purpose and include_sensitive_details. The description adds only the scoping meaning of show_id (catalog of that show's artists), which the schema itself does not state, and nothing about the search or limit parameters.

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 and resource (busca músicas do catálogo dos artistas do show) plus the intended outcome (montar o setlist) and the returned fields. It implicitly distinguishes itself from music360_get_show_setlist by being a candidate/catalog lookup rather than the setlist itself, though it never names that sibling.

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?

The phrase 'para montar o setlist' implies when to use it (while assembling a setlist), but there is no explicit exclusion or routing to alternatives such as music360_get_show_setlist or music360_list_fonograma. An agent must infer the boundary from the sibling names.

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