Skip to main content
Glama

BikerLink REAL

bikerlink_get_place

Read-only

Get public information including image_url and hub_graphic_url for one active Punto Biker or Smart Station by code, e.g. PB-00002 or SS-00002. When present, verified_data contains published BikerLink services, prices, offers and the verification date. ONLY human_verified:true with verification_label VERIFICATO DA AGENTE UMANO — BIKERLINK REAL indicates an explicitly attested on-site human visit; never assume other records are verified in person.

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": {
      "code": "<code>"
    },
    "name": "bikerlink_get_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses the returned field set (image_url, hub_graphic_url, verified_data with services, prices, offers and verification date) and, crucially, the verification semantics: only human_verified:true with the specific VERIFICATO DA AGENTE UMANO label means an attested on-site visit. That warning is behavioral context an agent cannot derive from the schema and prevents a real misinterpretation.

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 what the tool returns, then the conditional verified_data note, then the verification caveat. Three sentences, each carrying weight, though the final sentence is dense and slightly repetitive in its emphasis on never assuming verification.

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?

With no output schema, the description substitutes well by enumerating the key return fields and their conditional presence. The main gap is failure behavior for a nonexistent or inactive code, which the 'active' wording gestures at but never resolves.

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?

With 0% schema description coverage, the description carries the burden and mostly does: it explains that the code identifies one Punto Biker or Smart Station and gives concrete examples (PB-00002, SS-00002), which maps the PB/SS prefixes to meaning that the bare regex pattern does not convey. The 'active' qualifier hints at a lookup constraint without explaining what happens for inactive codes.

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?

The description gives a specific verb and resource: retrieve public information (image_url, hub_graphic_url) for a single active Punto Biker or Smart Station identified by code. The singular 'by code' framing naturally separates it from the search-oriented siblings, but no sibling is named explicitly, so it stops short of a 5.

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 rather than stated: it is for lookups when you already have a PB-/SS- code, and search tools would be the alternative for discovery, but that is never spelled out. The conditional note that verified_data appears 'when present' is helpful guidance about output rather than about tool selection.

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