Skip to main content
Glama

get_emergency_facilities

Read-only

Nearby emergency facilities (hospital, police, fire).

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": {
      "location": "<location>"
    },
    "name": "get_emergency_facilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
locationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. Beyond that, the description only adds the facility categories; it says nothing about search radius, result limits, or how proximity is determined against the supplied location.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with zero wasted words and the resource is front-loaded. However, it is too terse to be a complete sentence and leaves essential context unstated rather than simply being efficient.

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

Completeness2/5

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

An output schema exists, so return values need not be described. But with two parameters at 0% schema coverage, one being a free-form nested location object and the other an undocumented 'type', the description leaves the agent without enough information to call 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 0% and the location parameter is an unconstrained nested object, so the description should clarify input format. The parenthetical 'hospital, police, fire' loosely hints at the purpose of the 'type' parameter, but it never states that 'type' filters results or what values are accepted, and location syntax (coordinates vs. address) remains unexplained.

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?

The description names a specific resource, 'emergency facilities', and enumerates the concrete kinds (hospital, police, fire) plus the 'nearby' scope. That is enough to distinguish it from weather/traffic siblings, but it does not differentiate it from find_nearby_places or explain what makes an emergency facility special.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to an alternative such as find_nearby_places for non-emergency POIs. The agent must infer usage entirely from the tool name.

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.