Skip to main content
Glama

Breadcrumb structured data

bpj_breadcrumb_structured_data
Read-onlyIdempotent

Turn the path from home to the current page into BreadcrumbList JSON-LD.

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": {
      "trail": "<trail>"
    },
    "name": "bpj_breadcrumb_structured_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
trailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so safety and side-effect behavior are covered. The description adds that the output is BreadcrumbList JSON-LD, but it does not describe validation, error behavior, or how the trail is parsed.

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. It is appropriately sized for a simple conversion tool, though brevity leaves gaps covered elsewhere.

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?

For a one-parameter, read-only conversion tool with no output schema, the description states purpose and output type adequately. However, it lacks usage guidance and does not explain the required input line format, so completeness is only moderate.

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%, so the description needs to explain the single required 'trail' parameter. It only says 'path from home to the current page' and omits the schema title's 'Level name | absolute URL per line' formatting and the 5000-character limit.

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 uses a specific verb ('Turn') and resource ('path from home to the current page') and names the output ('BreadcrumbList JSON-LD'). It is clear what the tool produces, though it does not explicitly distinguish itself from sibling structured-data tools such as article or FAQ generators.

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?

No when-to-use, when-not-to-use, or alternative-tool guidance is given. The only implied usage is generating breadcrumb JSON-LD from a trail; prerequisites and sibling selection are left to inference.

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.