Skip to main content
Glama
Sign In

Portugal (public data)

by io.github.ThiagoJacobLannes
OverviewDiscussionsAdmin

lisbon_recycling

The nearest recycling points in Lisbon of a given kind.

Args: lat, lon: where you are. kind: "ecoponto" (paper, plastic, glass), "vidrao" (glass), "papel", "oleo" (used cooking oil), "reee" (small electronics), "alimentar" (food waste), "ecoilha", "ecocentro" (large items). radius_m: search radius in metres (max 3000).

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "lisbon_recycling"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes
kindNoecoponto
limitNo
radius_mNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It adds useful constraints: results are nearest, radius is capped at 3000 m, and kind accepts specific categories. However, it does not state that this is a read-only lookup, how many results are returned, or how limit interacts with nearest sorting.

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?

The purpose is front-loaded in one sentence, followed by a compact Args list. Every line adds useful information, and there is no redundant prose.

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?

The description covers the core location and kind semantics and notes the radius maximum; an output schema exists, so return values need not be explained. For a five-parameter, annotation-free tool, however, the missing limit behavior and omitted defaults leave the definition incomplete enough to risk incorrect invocation.

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%, so the description must explain all five parameters. It gives meaning to lat/lon, maps kind values to waste streams, and gives the radius cap, but it omits the limit parameter and does not mention any defaults. This is helpful but incomplete compensation.

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 first sentence gives a specific action, resource, and location: nearest recycling points in Lisbon, filtered by kind. It is clearly distinct from sibling tools such as events, transit, or fuel prices. An agent can identify the task without opening the 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?

The description implies use when you have a location and want the nearest recycling point of a given type, but it never states when to choose this over alternatives or any exclusions. There are no closely related recycling siblings, so alternatives are less critical, but guidance remains implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Portugal (public data) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources