Skip to main content
Glama

Puntos de recogida

listar_puntos
Read-onlyIdempotent

Puntos de recogida de ALD Mobility con su horario, zona, suplemento y si admiten entrega en hotel.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so safety is covered. The description still adds value by disclosing the shape of the returned data (hours, zone, surcharge, hotel-delivery flag), which matters because there is no output schema. It stops short of saying how many points come back or whether results are unfiltered, so it is not a full behavioral picture.

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?

A single front-loaded sentence with no filler: resource first, then the returned fields. Every clause carries information an agent would otherwise have to discover by calling the tool.

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 zero-argument, read-only catalog lookup with no output schema, stating the returned fields is close to sufficient. The only meaningful gap is that it does not say whether the list is global or scoped (e.g. by city), which would affect how the agent presents or filters results.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not imply any hidden inputs, which keeps the empty schema consistent.

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?

Names a specific resource (ALD Mobility pickup points) and enumerates the attributes it carries: horario, zona, suplemento, entrega en hotel. The retrieval verb is only implied by the bare noun phrase, but an agent can still tell this returns a list of pickup locations, which is clearly distinct from the sibling tools about vehicles, budgets and conditions.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no pointer to an alternative tool. The agent must infer from the sibling names that this is the lookup to run before calcular_presupuesto or consultar_condiciones, and nothing in the description confirms or denies that ordering.

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