Skip to main content
Glama

Music360 MCP

by br.com.music360.app
OverviewDiscussionsAdmin

music360_get_fonograma

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYespublic_uid do registro. Não use ID numérico interno.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesDados completos do registro.
successYesIndica se a operacao foi bem-sucedida.
entity_idYespublic_uid do registro encontrado.
entity_typeYesTipo da entidade consultada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, placing the burden on the description. The verb 'consulta' indicates a read operation, and 'tenant atual' provides scoping context. However, it does not disclose details such as permission requirements for sensitive profiles or behavior when the record is not found, relying instead on schema descriptions.

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, succinct sentence that front-loads the action and resource. There is no wasted wording or redundant information, making it highly efficient.

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 straightforward get-by-id tool with an output schema, the description covers the core purpose and scoping. It lacks mention of optional sensitive-data parameters, but these are fully documented in the input schema, so the description remains sufficiently complete.

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 the baseline is 3. The description adds no new parameter semantics beyond what is already in the schema; it merely restates the constraint about using public_uid, which the 'id' parameter description already covers.

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 uses a specific verb ('Consulta' - queries), identifies the resource ('registro de fonograma'), and scopes it ('do tenant atual'). It clearly distinguishes from sibling tools like list_fonograma and search by emphasizing the use of only public_uid for a single record lookup.

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 context: use this when you have a public_uid and need a single record from the current tenant. However, it does not explicitly mention alternatives or when-not-to-use scenarios, such as needing to list multiple records or search by other criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Music360 MCP toolsInspect
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