Skip to main content
Glama
Sign In

Arrumou Neural

by io.github.brunoreisportela
OverviewDiscussionsAdmin

Remover bloqueio

remove_block
Destructive

Remove um bloqueio de datas. Bloqueios importados do Airbnb voltam na próxima sincronização se o anúncio continuar indisponível. Exige aprovação.

Escopo: calendar:write · Risco: consequential (prévia + aprovação do usuário obrigatória) · Efeitos: Apaga o RoomBlock 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": {
      "block_id": "<block_id>"
    },
    "name": "remove_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idYes
approval_idNoId de uma aprovação já decidida pelo usuário para esta mesma ação. Omita para receber a prévia e o link de aprovação.
idempotency_keyNoChave de idempotência escolhida pelo cliente; repetir a chave com os mesmos dados devolve o mesmo resultado.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the concrete effect (the RoomBlock is deleted and an activity record is written), the required preview-plus-approval flow, the calendar:write scope, the 'consequential' risk tier, and the Airbnb re-sync caveat. The destructiveHint annotation only says 'destructive'; the description explains what is destroyed and what side effects accompany it.

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?

Two tight sentences followed by a compact scope/risk/effects line. The most decision-relevant facts (removal, sync caveat, approval requirement, unavailability) are front-loaded with minimal waste, though mixing prose with a metadata run-on is slightly harder to parse.

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?

With no output schema, the description covers the return-relevant points an agent needs: a preview/approval link is returned when approval_id is omitted, and the operation is audited. The only real omission is how to source a valid block_id, which matters for a single-required-parameter destructive tool.

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 coverage is 67%: approval_id and idempotency_key are already documented in the schema, and the description only adds context for approval_id via the preview/approval requirement. block_id is undocumented in the schema and the description does not say where it comes from or what format it takes, so the coverage gap is not compensated.

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: 'Remove um bloqueio de datas' and clarifies it deletes a RoomBlock. An agent can distinguish it from block_dates (create) and list_blocks (read) by the verb alone, though the description never names those siblings explicitly.

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 clear operating conditions: user approval is mandatory, a preview must be obtained first, and the tool is currently unavailable under this authorization. It also warns that Airbnb-imported blocks reappear on the next sync, which effectively tells the agent when the action is futile. It does not, however, point to list_blocks as the way to obtain a block_id.

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