Skip to main content
Glama
Sign In

Arrumou Neural

by io.github.brunoreisportela
OverviewDiscussionsAdmin

Cotar estadia

quote_stay
Read-onlyIdempotent

Cotação por noite para uma categoria, ocupação e período, usando o tarifário vigente (tarifa base ou plano). Não cria reserva.

Escopo: calendar:read · Risco: read · Efeitos: Nenhum.

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": {
      "category_id": "<category_id>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "quote_stay"
  }
}

Input Schema

NameRequiredDescriptionDefault
paxNo
plan_idNo
check_inYes
check_outYes
category_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds that no reservation is created and that current pricing is used, but it largely repeats the risk/effects metadata and does not explain the quote response or error behavior.

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 description is front-loaded and compact: two substantive sentences plus a short scope line. The scope/risk/effects line slightly duplicates annotation information, but it is not verbose.

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 five-parameter pricing tool with no output schema, the description is minimally adequate but incomplete. It does not describe what the quote response contains, how pax or plan_id affect the quote, or what happens on invalid dates or missing rates.

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?

With 0% schema description coverage, the description partially compensates by mapping categoria, ocupação, período, and plano/tarifa to the parameters. However, it omits details such as pax defaults/min/max, date format expectations, and optionality of plan_id.

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 description states a specific action ("Cotação por noite") and the resource/scope (categoria, ocupação, período, tarifário vigente), and explicitly clarifies that it does not create a reservation. It distinguishes itself from create_reservation but does not compare itself to the likely alternative get_availability.

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?

"Não cria reserva" implies that booking should use create_reservation, but there is no explicit when-to-use/when-not-to-use guidance. It does not tell the agent when to use this versus get_availability or list_categories.

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