Music360 MCP

music360_list_tarefa

Lista registros de tarefa do tenant atual.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No
`search`	No
`order_by`	No	Campo para ordenacao (ex.: data_lancamento/lancamento, nome, atualizacao, criacao). Para produto fonografico, "lancamento" e "mais recente" significam data_lancamento. Quando omitido, usa ordenacao padrao da entidade.
`per_page`	No
`order_dir`	No	Direcao da ordenacao: ASC crescente, DESC decrescente (padrao).
`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	Resultado paginado.
`success`	Yes	Indica se a operacao foi bem-sucedida.
`entity_type`	Yes	Tipo da entidade consultada.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJun 7, 2026

addedInput schema / properties / include_sensitive_details

Added value: +{
+  "description": "Retorna detalhes sensíveis mínimos quando autorizado por escopo admin. Padrão: false.",
+  "type": "boolean"
+}

addedInput schema / properties / response_profile

Added value: +{
+  "description": "Perfil de resposta. Listagens usam summary por padrão; sensitive exige admin.",
+  "enum": [
+    "summary",
+    "standard",
+    "sensitive"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sensitive_access_purpose

Added value: +{
+  "description": "Finalidade operacional obrigatória quando response_profile=sensitive ou include_sensitive_details=true.",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Resultado paginado.",
+      "properties": {
+        "data": {
+          "description": "Lista de registros encontrados.",
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "page": {
+          "type": "integer"
+        },
+        "per_page": {
+          "type": "integer"
+        },
+        "total": {
+          "type": "integer"
+        },
+        "total_pages": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "data",
+        "total",
+        "page",
+        "per_page",
+        "total_pages"
+      ],
+      "type": "object"
+    },
+    "entity_type": {
+      "description": "Tipo da entidade consultada.",
+      "type": "string"
+    },
+    "success": {
+      "description": "Indica se a operacao foi bem-sucedida.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "entity_type",
+    "data"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 3, 2026

changedInput schema / properties / order_by / description

Previous value: -"Campo para ordenacao (ex.: data_lancamento, nome, atualizacao, criacao). Quando omitido, usa ordenacao padrao da entidade."New value: +"Campo para ordenacao (ex.: data_lancamento/lancamento, nome, atualizacao, criacao). Para produto fonografico, \"lancamento\" e \"mais recente\" significam data_lancamento. Quando omitido, usa ordenacao padrao da entidade."

First observedJun 3, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Lista' (lists) but does not state whether the operation is read-only, whether it supports pagination, or the implications of parameters like response_profile or include_sensitive_details. No behavioral traits beyond the basic action are disclosed.

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, direct sentence with no extraneous content, placing the key information (lists task records, tenant scope) upfront. It is appropriately sized for the minimal information it conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 8 parameters and no annotations, the description provides only the basic action and entity scope. It omits critical context about pagination, default ordering, sensitive data handling, and differences from related list/get tools, making it insufficient for an agent to fully understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers 63% of parameters with descriptions, leaving page, search, and per_page unexplained. The description itself adds no parameter-level information, so it neither leverages existing descriptions nor compensates for the gaps.

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 'Lista registros de tarefa do tenant atual' (Lists task records from the current tenant), using the specific verb 'Lista' and resource 'registros de tarefa.' This distinguishes it from sibling tools like music360_get_tarefa, which retrieves a single record, and other list tools for different entity types.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as music360_get_tarefa for individual records or music360_search for broader queries. It only mentions the tenant scope, leaving out any explicit context about intended use cases or 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?