Skip to main content
Glama

BikerLink REAL

bikerlink_search_verified_services

Read-only

Search published BikerLink REAL services and offers from active PB and SS locations. Only records explicitly marked human_verified:true and verification_status:verified_by_human_agent have been verified on site by a human agent. Other records may be confirmed by the manager or by phone. Prices and availability refer to the stated verification date, not real time.

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_verified_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
regionNo
serviceNo
categoryNo
provinceNo
free_onlyNoShow only activities with a verified free service/offer matching the requested service
municipalityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds real value on top: it defines the exact verification flags (human_verified:true, verification_status:verified_by_human_agent), warns that other records are only manager- or phone-confirmed, and clarifies that prices/availability are as of the verification date rather than live. It stops short of describing result ordering or pagination behavior.

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?

Four short sentences, front-loaded with the core action and followed by the verification caveat that most affects interpretation of results. No filler or repetition, though the verification explanation could be tightened slightly.

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 verification semantics are handled well for a read-only search, and no output schema exists so return values need not be described. However, with 8 loosely documented parameters at 13% coverage, an agent still cannot tell what PB/SS mean or how the geographic filters compose, which is a material gap for this tool.

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

Parameters2/5

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

Schema description coverage is only 13% — just free_only is documented — so the description needs to compensate and does not. It never defines the type enum values PB/SS, never distinguishes region from province from municipality, and says nothing about limit, service, or category, leaving 8 parameters largely opaque.

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?

States a specific verb and resource ("Search published BikerLink REAL services and offers") plus a scope qualifier (active PB and SS locations), which is enough to separate it from the place-oriented siblings bikerlink_search_places and bikerlink_get_place. It does not name a sibling explicitly, so differentiation is implicit 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?

Usage is implied: the description frames the tool as the way to find services/offers and explains that non-verified records also exist, so an agent can infer when verification matters. There is no explicit when-to-use versus when-not guidance, no mention of bikerlink_search_places as an alternative for venue lookup, and no prerequisites.

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