Skip to main content
Glama

Check whether a parent needs urgent help

get_help
Read-onlyIdempotent

Checks a parent's message for signs it needs urgent help (emergency, poison, fever in a young baby, breathing, self-harm and similar) and returns who to call and the reviewed warning signs for each stage. Call it first whenever a message mentions a symptom, an injury, something swallowed, or a parent struggling. With no text, it returns the numbers and warning signs.

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_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoThe parent's message, as written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value annotations cannot: the empty-input behavior ("with no text, it returns the numbers and warning signs") and the shape of the response (contacts plus reviewed warning signs per stage). It does not describe scoring thresholds or how ambiguous messages are handled.

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, front-loaded with the core action, then the usage trigger, then the edge case. No redundancy and nothing that could be cut without losing meaning.

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

Completeness4/5

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

For a one-parameter read-only tool with no output schema, the description covers purpose, triggers, and return content, which is enough to invoke it correctly. The only remaining gap is what happens for a message judged non-urgent, which an agent may still wonder about.

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?

Schema coverage is 100% with a single optional parameter, so the baseline would be 3. The description goes further by explaining the meaning of omitting it — calling with no text still returns phone numbers and warning signs — which is behavior the schema cannot express.

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 a parent's message for urgent-help signals — and enumerates the signal categories (emergency, poison, fever in a young baby, breathing, self-harm). It also declares the return content (who to call, reviewed warning signs per stage), which cleanly separates it from the guide-lookup siblings.

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?

"Call it first whenever a message mentions a symptom, an injury, something swallowed, or a parent struggling" gives concrete invocation triggers and a priority ordering. It stops short of naming when-not conditions or pointing at the siblings (list_guides/read_guide) for non-urgent follow-up, so it is clear context rather than a full decision rule.

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