Music360 MCP

music360_get_produto_fonografico

Consulta um registro de produto fonográfico 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.

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": "Dados completos do registro.",
+      "type": "object"
+    },
+    "entity_id": {
+      "description": "public_uid do registro encontrado.",
+      "type": "string"
+    },
+    "entity_type": {
+      "description": "Tipo da entidade consultada.",
+      "type": "string"
+    },
+    "success": {
+      "description": "Indica se a operacao foi bem-sucedida.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "entity_type",
+    "entity_id",
+    "data"
+  ],
+  "type": "object"
+}

First observedJun 3, 2026

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. 'Consulta' indicates a read-only operation, which is helpful, but the description does not disclose authorization requirements for sensitive profiles, error behavior, or any other side effects beyond the basic read intent.

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, well-structured sentence that starts with the verb and resource, including the key distinguishing detail (public_uid) without any unnecessary 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?

For a simple single-record lookup, the description combined with the complete input schema and presence of an output schema is sufficient. It does not explicitly cover sensitive-access workflows, but those are fully described in the parameter properties.

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?

The schema already documents all parameters with 100% coverage. The description adds a slight constraint with 'usando somente public_uid' and tenant scoping, but these are largely echoed in the schema descriptions. There is no substantial added meaning.

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 is specific: it names the verb 'Consulta', the resource 'registro de produto fonográfico', the tenant scoping, and the retrieval method 'usando somente public_uid'. This clearly distinguishes it from the list sibling (music360_list_produto_fonografico) and from 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 clearly implies single-record retrieval by public_uid, which contrasts with list alternatives. However, it does not explicitly mention when not to use the tool or name alternative tools, so it stops short of full guidance.

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?