Skip to main content
Glama

BikerLink REAL

bikerlink_search_places

Read-only

Search publicly active Punti Biker and Smart Stations by name, location or code, including GPS coordinates, pass page, public PhotoPass URL and public image_url / hub_graphic_url for displaying the location. 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

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

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
queryNo

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 readOnly/openWorld=false/destructive=false, so the safety profile is covered; the description earns credit for far more than that. It enumerates the returned fields (GPS coordinates, pass page, PhotoPass URL, image URLs), explains what verified_data holds when present, and gives a strong interpretive warning that only human_verified:true with the specific VERIFICATO label means an attested visit. It does not mention result volume or pagination behavior, keeping 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?

Three sentences, front-loaded with the action, followed by return-content detail and then the most safety-critical caveat placed last for emphasis. The field enumeration (image_url / hub_graphic_url) is slightly list-heavy but justified because no output schema exists; nothing is redundant.

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, describing the returned payload and the meaning of verified_data is exactly what an agent needs, and the human-verification warning prevents a costly misinterpretation. The remaining gap is the undocumented `type` enum and `limit` cap, which an agent must infer or discover from the schema alone.

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 carries the burden. It clarifies the `query` parameter by naming the three searchable dimensions (name, location, code) and the mention of 'Punti Biker and Smart Stations' implicitly maps to the PB/SS values of `type`, but the enum is never explained and the `limit` parameter is not addressed at all. This is only partial compensation for a fully undocumented schema.

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 opens with a specific verb and resource — 'Search publicly active Punti Biker and Smart Stations by name, location or code' — which lets an agent understand the operation immediately. It implicitly distinguishes itself from bikerlink_search_verified_services through the scope word 'places' and the 'publicly active' qualifier, but it never names the sibling explicitly, so the differentiation is inferential rather than stated.

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 'publicly active' scope and the ability to search by name, location or code imply the usage context, and the verification caveat signals that this tool should not be relied on for confirmed on-site visits. However, there is no explicit when-to-use / when-not-to-use guidance and no alternative tool is named for cases such as fetching a single place or searching only verified services.

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