Arrumou Neural

Solicitar sincronização

start_sync

Cria uma solicitação de sincronização do Airbnb que a extensão exibe ao usuário; a coleta só começa quando o usuário confirma no painel da extensão no multicalendário do Airbnb. Devolve um job para acompanhar (get_job).

Escopo: sync:execute · Risco: low · Efeitos: Cria AgentJob airbnb_sync em awaiting_extension. · Pré-requisitos: Extensão pareada e online; Habitações com link do Airbnb · INDISPONÍVEL nesta autorização (escopo não concedido ou papel sem o módulo)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`prices`	No
`device_id`	No	Obrigatório quando há mais de um navegador pareado.
`occupation`	No
`reservations`	No
`duration_days`	No		180
`habitation_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that the call only enqueues an AgentJob in 'awaiting_extension' state, that actual collection is gated on user confirmation, the required scope (sync:execute), the risk level, and even the current authorization state of the tool. The annotations (non-read-only, non-idempotent, non-destructive, open-world) are consistent with this.

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?

Front-loaded purpose sentence followed by a compact structured line for scope, risk, effects, and prerequisites. Every sentence carries information; the authorization-status note is slightly meta but still actionable for an agent deciding whether calling is pointless.

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?

No output schema exists, and the description compensates by saying a job is returned for tracking via get_job. Combined with the async/human-confirmation model and prerequisites, an agent knows enough to call it correctly, with the parameter meanings being the remaining hole.

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?

Six parameters at 17% schema description coverage, yet the description says nothing about prices, occupation, reservations, duration_days, or habitation_ids. With such low schema coverage the description needed to compensate for what each flag controls and what the defaults mean, and it does not.

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?

States a specific verb and resource ('Cria uma solicitação de sincronização do Airbnb') plus the key mechanic that no data is collected until the user confirms in the extension. It does not explicitly distinguish itself from 'preview_sync' or 'list_sync_jobs', which are the closest siblings, so it falls short of a 5.

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

Usage Guidelines4/5

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

Gives real usage context: prerequisites (extension paired and online, properties with an Airbnb link) and the human-in-the-loop confirmation step that must happen before collection. It never states when to choose this over preview_sync or list_sync_jobs, so no exclusions or alternatives are provided.

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.