Skip to main content
Glama
Sign In

Arrumou Neural

by io.github.brunoreisportela
OverviewDiscussionsAdmin

Histórico de mensagens

list_guest_messages
Read-onlyIdempotent

Mensagens registradas para uma estadia.

Escopo: messages:draft · Risco: read · Efeitos: Nenhum. · 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": {
      "reservation_id": "<reservation_id>"
    },
    "name": "list_guest_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
reservation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the description's 'Risco: read · Efeitos: Nenhum' largely restates them. The one genuine addition is the required scope ('messages:draft') and the conditional availability warning, which is useful context an agent could not get from the annotations.

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

Conciseness3/5

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

The description is short, but the space is spent on boilerplate scope/risk/effect metadata rather than on what the tool returns or how to call it. The availability flag is buried at the end after generic labels.

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?

For a single-parameter read tool with no output schema, the description should say what messages are returned (drafts? sent? full thread?) and which key scopes the result. It leaves both the parameter and the return semantics unaddressed, and the availability note raises as many questions as it answers.

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% and there is exactly one required parameter, reservation_id, which the description never mentions or explains. With no compensation for the undocumented parameter, it falls below the 0-param baseline of 4.

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

Purpose3/5

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

The description identifies the resource ('Mensagens registradas para uma estadia') but never states the operation (list/retrieve) and offers no differentiation from siblings like list_message_templates, draft_guest_message, or send_guest_message. An agent must infer from the tool name that this is a read/list of message history scoped to a reservation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this instead of draft_guest_message, send_guest_message, or list_message_templates. The only qualifier is an availability warning ('INDISPONÍVEL nesta autorização'), which is a caveat rather than a usage rule and gives no positive selection criteria.

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