Arrumou Neural

Editar cliente

update_guest

Atualiza o cadastro de um cliente (campos informados substituem os atuais).

Escopo: guests:write · Risco: low · Efeitos: Atualiza Customer e registra atividade. · INDISPONÍVEL nesta autorização (escopo não concedido ou papel sem o módulo)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "update_guest"
  }
}

Input Schema

Name	Required	Default
`id`	Yes
`city`	No
`type`	No	person
`email`	No
`phone`	No
`state`	No
`mobile`	No
`country`	No
`birthday`	No
`last_name`	No
`first_name`	No
`trade_name`	No
`nationality`	No
`document_type`	No
`internal_notes`	No
`document_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A3.5/5.0

Behavior5/5

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

The description is extremely transparent. It specifies the exact data replacement policy (fields replace current ones), the effect (registers activity), and the necessary security scope (guests:write). These details go well beyond what the annotations cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core function is stated first, making it easy to parse. Although the auxiliary information (Escopo, Risco, Efeitos) is separated into distinct points, the overall structure is efficient and easy to scan.

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?

Given the complexity of 16 parameters and 0% schema description coverage, the tool definition is incomplete. It provides a high-level summary but fails to provide sufficient guidance for the agent to know which parameters are most critical or constrained.

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?

Schema description coverage is 0%. Since there are 16 parameters, the description must compensate heavily. Instead, it uses a generic statement ('campos informados') without guiding the agent on the intent of specific, complex fields like `document_type` or `nationality`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The purpose is clear: updating a customer/guest registration ('Atualiza o cadastro de um cliente'). While the verb and resource are clear, the description lacks differentiation from the large list of 'list' or 'create' siblings.

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 by stating 'campos informados substituem os atuais' (provided fields replace current ones). It also clarifies the limitations regarding authorization and scope ('INDISPONÍVEL nesta autorização'), providing clear constraints on when the tool can be successfully used.

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

All Arrumou Neural 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.