Music360 MCP

music360_get_tarefa

Consulta um registro de tarefa do tenant atual usando somente public_uid.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	public_uid do registro. Não use ID numérico interno.
`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	Dados completos do registro.
`success`	Yes	Indica se a operacao foi bem-sucedida.
`entity_id`	Yes	public_uid do registro encontrado.
`entity_type`	Yes	Tipo da entidade consultada.

TDQS

A4/5.0

Behavior3/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 discloses that the lookup uses only public_uid and is scoped to the current tenant, but it does not explicitly state read-only behavior, auth requirements, or potential error semantics. The verb 'consulta' implies read-only, but more disclosure would be safer.

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?

A single, focused sentence that front-loads the verb and resource. No wasted words, and it directly addresses the core operation.

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?

The description, combined with a complete input schema and existing output schema, is sufficient for a straightforward get-by-id tool. It lacks some usage guidance, but the essential context of scope and identifier is present.

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 100% with all parameters described. The description adds no new meaning beyond reinforcing the 'public_uid' requirement for the id parameter. Baseline 3 is appropriate since the schema does the heavy lifting.

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 verb (consulta), the resource (registro de tarefa), the scope (tenant atual), and the required key (public_uid). It effectively distinguishes this get operation from list/search siblings and other entity-specific get tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: use this when needing a single task record and possessing its public_uid. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous enough for an agent to infer when to select it.

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?