Skip to main content
Glama

Ver se o plantão está atendendo agora

verificar_plantao
Read-onlyIdempotent

Checks whether Doutor Chamada's on-call doctors are seeing patients right now (by the service hours, in Brasília time) and, if closed, when it reopens. Use when someone asks if there is a doctor available now or what the hours are. Takes no input.

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": "verificar_plantao"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
textoYes
abertoYes
horarioYes
reabreEmYes
emergenciaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds context beyond them: the answer is computed from service hours in Brasília time, and when closed it also reports the reopening time — useful behavioral detail an agent could not infer from annotations. It stops short of describing latency, caching, or error conditions, which keeps it from a 5.

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?

Two sentences, both earning their place: the first defines the check and the time basis, the second gives the usage trigger. The purpose is front-loaded and there is no redundant wording.

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?

For a zero-parameter availability check with full annotation coverage and an output schema, the description supplies everything needed: what is checked, the timezone the hours are evaluated in, what is returned when closed, and when to call it. Return-value formatting is correctly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. 'Takes no input' merely confirms what the schema already shows; no further parameter meaning is needed or expected.

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?

States a specific verb and resource ('Checks whether Doutor Chamada's on-call doctors are seeing patients') plus the precise scope of the check (service hours, Brasília time) and the fallback information returned when closed. An agent can immediately tell this is a schedule/availability lookup, distinct from the sibling tools, which concern starting a consultation, listing consultation options, and asking questions.

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 an explicit trigger: 'Use when someone asks if there is a doctor available now or what the hours are.' This covers both the availability question and the hours question, leaving little to inference. It does not name exclusions or point to an alternative, but the siblings listed are clearly unrelated, so that omission is minor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources