Skip to main content
Glama

BikerLink REAL

bikerlink_photo_pages

Read-only

Find public PhotoPass/photo gallery links associated with active Punti Biker. Includes the public PB image_url and hub_graphic_url; no individual photos, photo availability dates, galleries or purchases are indexed here.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

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 declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful disclosure beyond that: the result set is limited to 'active' Punti Biker, returns public image URLs, and explicitly excludes photo-level data, availability dates and purchase information.

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?

Two tight sentences, front-loaded with the core action and scope, with no filler. Minor cost: undefined shorthand ('PB') and an unexplained field name ('hub_graphic_url') slightly reduce immediate comprehension.

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 inclusion/exclusion scope is well covered and no output schema exists to require return-value explanation, so the main body is adequate. The complete silence on the two input parameters leaves a meaningful gap for a tool whose only knobs are filtering and paging.

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 0% for both parameters, and the description never mentions 'limit' or 'query'. An agent gets no explanation of what 'query' matches against (owner name, gallery name, location?) or how results are capped, so the schema burden is not compensated.

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: find public PhotoPass/photo gallery links, scoped to 'active Punti Biker', and names the returned fields (PB image_url, hub_graphic_url). It does not explicitly contrast with the sibling place-search tools, so differentiation is left to the domain wording 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 'no individual photos, photo availability dates, galleries or purchases are indexed here' clause functions as a negative boundary about scope, which helps an agent avoid misusing it. However, there is no explicit when-to-use guidance or named alternative tool for those excluded needs.

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