Skip to main content
Glama

Music360 MCP

by br.com.music360.app
OverviewDiscussionsAdmin

music360_get_contato

Consulta um registro de contato 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

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose an important constraint: only public_uid may be used, not the internal numeric ID. However, it does not mention authorization requirements for sensitive details, error behavior, or other side effects, which are relevant given the sensitive parameters in the schema.

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, clear sentence that is front-loaded with the verb 'Consulta'. It contains no filler and effectively communicates the core purpose without unnecessary detail.

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 captures the essential use case and scope. The output schema and parameter descriptions cover return values and optional parameters, so the description is adequately complemented by structured data. It could mention the sensitive options, but the schema already explains them.

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 all parameters are already well-documented. The description adds no new semantic detail about parameters; it merely reinforces the id requirement ('somente public_uid'), which is already in the schema.

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 action: 'Consulta um registro de contato do tenant atual' (queries a single contact record of the current tenant) with the specific identifier 'usando somente public_uid'. This distinguishes it from sibling 'get' tools (different entities) and 'list_contato' (singular vs. list).

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 for use: to fetch a single contact record by public_uid within the current tenant. It implies this tool is for singular lookups, but it does not explicitly mention alternatives or exclusion criteria (e.g., 'use list_contato for multiple records').

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