Skip to main content
Glama

Hospital departments and slots

get_hospital_departments
Read-only

Departments of a hospital listed on BinaSmart with consultation fee (ETB), doctors, hours, floor/room and appointment slots left for a date. Use the slug from search_places (is_hospital = true).

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": {
      "slug": "<slug>"
    },
    "name": "get_hospital_departments"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD (default today)
slugYesHospital slug from search_places

Output Schema

NameRequiredDescriptionDefault
dateNoDate the slots are for (YYYY-MM-DD)
demoNotrue for a demo listing
book_urlNoAppointment page
hospitalNoHospital
source_urlNobina.et page this result comes from; cite it
demo_noticeNoShown when the listing is a demo
departmentsNoDepartments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "book_url": {
      +      "description": "Appointment page",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "date": {
      +      "description": "Date the slots are for (YYYY-MM-DD)",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "demo": {
      +      "description": "true for a demo listing",
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "demo_notice": {
      +      "description": "Shown when the listing is a demo",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "departments": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "additionalProperties": true,
      +            "properties": {
      +              "floor": {
      +                "anyOf": [
      +                  {
      +                    "type": [
      +                      "number",
      +                      "string"
      +                    ]
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ],
      +                "description": "Floor"
      +              },
      +              "hours": {
      +                "description": "Opening hours",
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "name": {
      +                "description": "Department",
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "name_am": {
      +                "description": "Name in Amharic",
      +                "type": [
      +                  "string",
      +                  "null"
      +                ]
      +              },
      +              "room": {
      +                "anyOf": [
      +                  {
      +                    "type": [
      +                      "number",
      +                      "string"
      +                    ]
      +                  },
      +                  {
      +                    "type": "null"
      +                  }
      +                ],
      +                "description": "Room"
      +              },
      +              "slots_left": {
      +                "description": "Appointment slots left that day",
      +                "type": [
      +                  "number",
      +                  "null"
      +                ]
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Departments"
      +    },
      +    "hospital": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": true,
      +          "properties": {
      +            "city": {
      +              "description": "City",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "name": {
      +              "description": "Name",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "name_am": {
      +              "description": "Name in Amharic",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "sub_city": {
      +              "description": "Sub-city",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Hospital"
      +    },
      +    "source_url": {
      +      "description": "bina.et page this result comes from; cite it",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context the annotations do not: it discloses the returned field set (fee, doctors, hours, location, live slot availability) and the cross-tool slug dependency, though it says nothing about pagination or how stale the slot data is.

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 dense sentences with zero filler; the resource and its output are front-loaded and the prerequisite is deferred to the trailing sentence where it belongs. Nothing repeats the name or title.

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 read-only lookup with an output schema, complete param coverage, and only two inputs, this says everything an agent needs: what comes back, the optional date scoping, and where the required slug originates. No material gap remains.

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 both parameters are already documented, including the date pattern and 'default today' semantics. The description only reinforces slug provenance, matching the baseline 3 when the schema does the heavy lifting.

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 names a specific verb+resource (departments of a hospital) and enumerates the exact payload — consultation fee in ETB, doctors, hours, floor/room, and remaining appointment slots for a date. That specificity lets an agent distinguish this detail-lookup from a broader discovery tool like search_health without opening the schema.

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 states the prerequisite explicitly: 'Use the slug from search_places (is_hospital = true)', which routes the agent to the correct upstream sibling. It stops short of naming when NOT to use it or how it differs from search_health, so it is clear context rather than 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources