Skip to main content
Glama
Sign In

BridgesAgents

by com.bridgesagents
OverviewDiscussionsAdmin

Ver horários e datas livres

check_availability
Read-onlyIdempotent

Agenda em tempo real de um serviço, reserva, aluguel ou visita a imóvel ou veículo numa loja, antes de create_cart. Imóvel (kind PROPERTY) e veículo (kind VEHICLE): slots com os horários livres para visitar ou fazer test drive (uma visita por horário); use um start como scheduledFor. Serviço (kind SERVICE): slots com os horários livres (start e end, com fuso) dentro do horário da loja e quantas vagas sobram (free); use um start como scheduledFor. hoursKnown falso: a loja não cadastrou horário e confirma o pedido. Reserva (kind BOOKABLE): nights com cada noite e as vagas livres (free 0 = lotado); checkIn é a primeira noite e checkOut o dia seguinte à última. Aluguel (kind RENTAL): nights traz cada dia e as unidades livres; o aluguel ocupa do dia da retirada ao da devolução.

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": {
      "storeId": "<storeId>",
      "productId": "<productId>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoQuantos dias olhar (1 a 31; padrão 7)
fromNoPrimeiro dia (AAAA-MM-DD); hoje se vazio
storeIdYesstoreId da loja (de get_offers)
productIdYesproductId do serviço ou da reserva (de search_products)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, and the description adds substantial context beyond that: per-kind return semantics, free-slot counts, 'free 0 = lotado', one visit per slot, hoursKnown false behavior, and rental occupancy from pickup to return. This is rich behavioral disclosure for an availability check.

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 with the core purpose and then organized by kind, which suits the tool's complexity. It is dense and somewhat long, but most sentences carry useful kind-specific behavior rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return shapes, and it does so for PROPERTY, VEHICLE, SERVICE, BOOKABLE, and RENTAL. Combined with the fully documented input schema and safety annotations, an agent has enough information to call and interpret the tool correctly.

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 the schema already documents days, from, storeId, and productId. The description adds meaning about output fields such as start, scheduledFor, checkIn, checkOut, nights, and free, but it does not add input-parameter semantics beyond the schema, so the baseline 3 is appropriate.

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

Purpose5/5

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

The description states a specific verb and resource: real-time availability for a service, reservation, rental, property visit, or vehicle test drive. It also distinguishes the tool from create_cart by saying it is used before create_cart, and it explains the different availability shapes by kind.

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?

It gives clear usage context, including 'antes de create_cart' and how to use a start as scheduledFor, checkIn, and checkOut. It does not explicitly name alternatives such as get_offers or search_products or state when not to use this tool, so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BridgesAgents 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