Skip to main content
Glama
Sign In

Arrumou Neural

by io.github.brunoreisportela
OverviewDiscussionsAdmin

Disponibilidade por dia

get_availability
Read-onlyIdempotent

Estado de cada habitação por noite no período: available, booked (reserva ativa) ou blocked (bloqueio manual, Airbnb importado ou manutenção). Inclui origem, atualidade da última sincronização Airbnb e aviso de dados possivelmente desatualizados.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesÚltimo dia (exclusive). Máximo 190 dias.
start_dateYesPrimeiro dia (inclusive).
habitation_idsNoRestringe às habitações informadas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds meaningful domain behavior: it explains the status semantics and discloses that results include origin, Airbnb sync freshness, and a stale-data warning. This goes beyond the annotations without contradicting them.

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 definition is compact and front-loaded: the first sentence defines the per-night status output, the second adds provenance and freshness context, and the scope/risk line is brief. Every element contributes useful information.

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?

For a read-only availability query with rich annotations and fully described parameters, the description provides enough context about returned statuses, provenance, and freshness warnings. Because there is no output schema, it could more fully enumerate the response shape, but it is sufficient for correct selection and invocation.

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 parameter meanings such as inclusive start_date, exclusive end_date, 190-day maximum, and habitation_ids filtering are already documented. The description mentions the period and habitation scope only indirectly, adding little beyond the schema.

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 clearly states a specific resource and output: the state of each habitation per night over a date period, with enumerated statuses available/booked/blocked. It does not, however, differentiate itself from similar siblings such as get_occupancy_report or list_blocks.

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 explicit guidance on when to use this tool versus alternatives, nor any when-not conditions. The scope/permission line (calendar:read, read risk, no effects) is useful context but does not function as usage routing.

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