Music360 MCP

music360_list_contrato_partes

Lista as partes (contratado/contratante/interveniente) vinculadas a um contrato usando somente public_uid.

Input Schema

TableJSON Schema

Name	Required	Description
`contrato_id`	Yes	public_uid do contrato.
`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.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Lista de registros vinculados.
`success`	Yes	Indica se a operacao foi bem-sucedida.
`entity_id`	Yes	public_uid da entidade pai.
`sub_entity`	Yes	Tipo da sub-entidade listada.
`entity_type`	Yes	Tipo da entidade pai.

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the burden. It does not disclose behavioral traits such as read-only nature, permissions, or handling of sensitive data. The phrase 'usando somente public_uid' is about input, not behavior.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that is concise and to the point, with no wasted words.

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?

Given the simple listing nature and presence of a complete output schema, the description sufficiently covers the main purpose. It could mention sensitive profiles, but those are already documented in the schema.

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 baseline is 3. The description's reference to 'public_uid' merely echoes the schema's description for contrato_id without adding extra semantics.

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

Purpose5/5

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

The description clearly states the tool lists the parties (contracted/contracting/intervening) linked to a contract using public_uid. It is specific about the resource and verb, and distinguishes from sibling tools like list_contrato and get_contrato.

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 description implies usage when needing contract parties but does not explicitly provide alternatives or when-not-to-use cases. It mentions 'somente public_uid' but lacks direct comparison with sibling list/get tools.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose, targeting a specific entity or reference data. The get/list distinction is standard and unambiguous. Reference list tools are also clearly separated by domain.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with the prefix 'music360_'. Verbs are consistently 'get', 'list', 'search', or 'healthcheck', and the naming is uniform throughout. No mixed conventions or vague verbs.

Tool Count2/5

At 33 tools, the set is quite large, exceeding the threshold where tool count becomes unwieldy. While the domain has many entity types, the lack of mutation tools means many similar read-only list/get tools inflate the count without adding corresponding functionality.

Completeness1/5

The tool set is severely incomplete for a management system: there are no create, update, or delete tools for any entity. The reference list tools explicitly reference create tools like 'music360_create_fonograma' that do not exist, leaving clear dead ends and an inability to perform core operations.

Resources

Need Help?