Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_emergency_notdienst_info

Retrieve official 24/7 German Poison Control (Giftnotruf), US Poison Control (1-800-222-1222), UK NHS 111, medical on-call (116 117), and emergency pharmacies.

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

Input Schema

NameRequiredDescriptionDefault
city_or_stateNoCity or state (e.g. Köln, Bayern, Berlin, London, New York)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real behavioral context: the sources are 'official', availability is 24/7, and specific hotline numbers are surfaced. However, it does not disclose what happens when the city/state is unknown or outside DE/US/UK, whether results fall back to national numbers, or what the response looks like.

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?

One front-loaded sentence with no filler; the hotline numbers and service names are the substance rather than padding. It is dense but earns its length, though a short clause on optional location would have been more useful than some of the enumeration.

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

Completeness3/5

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

With no output schema and no annotations, the description does useful double duty by enumerating the kinds of contacts returned. It is still incomplete for the tool's complexity: fallback behavior for unsupported or missing locations and the optional nature of the location parameter are unaddressed.

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 single city_or_state parameter is already documented with examples in the schema. The description adds no meaning beyond it — notably it never says the parameter is optional or what the default behavior is when it is omitted.

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 uses a specific verb ('Retrieve') with a precisely scoped resource: official 24/7 poison control and emergency medical contacts, naming Giftnotruf, US Poison Control, NHS 111, 116 117, and emergency pharmacies. This is clearly distinguishable from unrelated siblings like get_fuel_station_prices_de or get_weather_and_civil_warnings. It stops short of a 5 because the geographic coverage (DE/US/UK only) is only implied by the examples rather than stated as a scope limit.

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

Usage Guidelines3/5

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

Usage is only implied by words like 'emergency' and '24/7' — an agent can infer this is for urgent medical/poisoning situations. There is no explicit when-to-use statement, no when-not-to-use, and no named alternative among the many sibling tools for non-emergency medical or local-service lookups.

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