Skip to main content
Glama

find_medicine_near

One-shot answer to "I need medicine X in city Y — what do I do?" in Portugal.

Runs medicine_availability(medicine) and pharmacies(city or lat/lon), and returns: the shortage status (compact), the pharmacies on duty today and the ones open now (nearest first when lat/lon are given), the help lines (Linha 1400, SNS 24, 112) and next steps. It never says a pharmacy has the medicine: stock is not public.

Args: medicine: Brand name or active substance, e.g. "quetiapina", "Brufen 400". city: Municipality or town, e.g. "Lisboa". Or give lat/lon instead. lat, lon: Optional user position (sorts pharmacies by distance). limit: Max pharmacies returned (default 8).

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": {
      "medicine": "<medicine>"
    },
    "name": "find_medicine_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
cityNo
limitNo
medicineYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full burden and does real work: it discloses the output contents (shortage status, on-duty and open-now pharmacies, help lines, next steps), the nearest-first ordering when lat/lon is supplied, and the critical caveat that stock is not public so it will never claim a pharmacy has the medicine. It omits read-only framing, failure behavior when neither city nor lat/lon is given, and any rate/coverage limits.

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?

Front-loaded with the user question it answers, then composition, then returns, then args — a logical scan order. The returns sentence is a dense run-on listing five outputs, which could be broken up, but no sentence is filler.

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 five-param aggregator with an output schema and no annotations, the definition covers composition, output shape, ordering, and the key stock caveat. Gaps are minor: no statement of what happens if neither city nor lat/lon is supplied, and no bounds guidance for limit beyond the default.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does: all five parameters are explained with format examples ('quetiapina', 'Brufen 400', 'Lisboa'), the default for limit, and the city-vs-lat/lon alternative. This adds meaning well beyond the bare typed properties.

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 composite action — running medicine_availability + pharmacies to answer one question — and names both underlying sibling tools. An agent can tell immediately this is an aggregator rather than a raw lookup, distinct from medicine_availability and pharmacies alone.

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?

The framing sentence ('I need medicine X in city Y — what do I do?') gives a clear trigger condition, and naming the two sibling calls it composes implies the alternative of calling those directly. It stops short of explicitly saying 'use the lower-level tools when you only need shortage status or pharmacy hours.'

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.