Skip to main content
Glama

Get Regional Emergency Eye Care & Sight-Loss Support Resources

get_eye_care_resources
Read-onlyIdempotent

Returns emergency telephone numbers, urgent ophthalmic triage pathways, clinical directories, and sight-loss charities tailored to the user's region ('us' United States, 'uk' United Kingdom, 'ie' Ireland, 'ca' Canada, 'anz' Australia & New Zealand, or 'global' International/Europe). Automatically infers region from edge geolocation if omitted.

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

Input Schema

NameRequiredDescriptionDefault
regionNoRegion code: 'us', 'uk', 'ie', 'ca', 'anz', or 'global'.

Output Schema

NameRequiredDescriptionDefault
regionIdYes
sectionsYes
regionLabelYes
resourcesUrlYes
emergencyNumberYes
emergencySummaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 genuine context beyond that: the categories of content returned and the fallback behavior of inferring region from edge geolocation when the parameter is omitted. It does not mention failure modes when geolocation is unavailable, which keeps it short of 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.

Conciseness4/5

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

Two sentences, front-loaded with the returned content before the region mechanics, with no filler. The dense parenthetical region mapping is information-bearing rather than padding, though it makes the sentence long enough to be slightly harder to scan.

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 single optional enum parameter, an output schema, and full annotation coverage, the description supplies everything an agent needs: what is returned, the valid region values and their meanings, and the inference behavior when omitted. Nothing required for correct invocation is missing.

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% and the enum is documented, but the schema only lists the raw codes while the description expands each into its meaning ('anz' = Australia & New Zealand, 'global' = International/Europe) and explains the omitted-parameter default. That is real added meaning over the structured field, though it stops short of guidance on which region to choose when the user is travelling.

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 uses a specific verb ('Returns') with a concretely enumerated resource set — emergency telephone numbers, triage pathways, clinical directories, sight-loss charities — so an agent knows exactly what comes back. The resource-directory nature is clearly distinct from the clinical siblings (list_eye_conditions, assess_visual_symptoms, simulate_vision) without needing to open any schema.

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 implied by the 'emergency' and 'sight-loss support' framing, so an agent can infer this is for urgent-care/support lookup rather than clinical assessment. However, there is no explicit statement of when to prefer this over the sibling symptom/condition tools, nor any exclusion such as 'do not use for diagnosis'.

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.