Skip to main content
Glama
Sign In

Arrumou Neural

by io.github.brunoreisportela
OverviewDiscussionsAdmin

Observações da estadia

update_reservation_notes

Atualiza observações internas ou a observação para a camareira de uma estadia (reversível, sem aprovação).

Escopo: reservations:write · Risco: low · Efeitos: Atualiza o campo 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>",
      "field": "<field>",
      "value": "<value>"
    },
    "name": "update_reservation_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
fieldYes
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses reversibility, no-approval behavior, required scope (reservations:write), risk level, that it logs activity, and critically that it is currently unavailable under this authorization. This is exactly the kind of operational context an agent needs before attempting a mutation.

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 purpose is front-loaded, and the dot-separated metadata is compact. No sentence is wasted, though the metadata block adds mild visual clutter and the final availability warning appears last rather than immediately after the purpose.

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

Completeness3/5

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

For a 3-parameter mutation with no output schema, the description covers behavior, reversibility, approval, and availability well. It falls short on explaining the `id` parameter and the `value` length constraint, which an agent would still need from the schema alone.

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%, so the description must carry parameter meaning. It implies the two values for the `field` enum ("observações internas" and "observação para a camareira") but does not explain `id` or the 2000-character limit on `value`, leaving most parameter semantics undocumented.

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 names a specific verb ("Atualiza") and precise resource ("observações internas ou a observação para a camareira de uma estadia"), and makes clear this is a notes-only mutation. An agent can easily distinguish it from siblings such as update_reservation_status or update_reservation_guests.

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 two note fields are named, implying when the tool applies, and the parenthetical "(reversível, sem aprovação)" gives useful context. However, it does not explicitly compare against alternatives (e.g., update_reservation_status or update_guest) or state when not to use it.

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

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