Skip to main content
Glama

XFN relationship link

bpj_xfn_relationship_link
Read-onlyIdempotent

Check relationship tokens against the XFN vocabulary and build a linked profile annotation.

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": {
      "name": "<name>",
      "url": "<url>",
      "relationship": "<relationship>"
    },
    "name": "bpj_xfn_relationship_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
relationshipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds that tokens are validated against a fixed vocabulary and that an annotation is produced, but it doesn't say whether invalid tokens cause an error or a partial result, nor what the returned annotation looks like.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity tips into under-specification given three undocumented required parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three required parameters, zero schema coverage, and no output schema, the definition leaves an agent unable to construct or interpret a call confidently. It should at minimum explain token format, validity handling, and the shape of the built annotation.

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 must carry parameter meaning, and it does not. It never explains what 'name' and 'url' are used for, nor what token syntax or combination rules 'relationship' accepts beyond the bare schema title.

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 names a specific verb and resource: check relationship tokens against the XFN vocabulary and build a linked profile annotation. That distinguishes it from the sibling link-checking tools (label check, new-tab check, canonical check), though 'linked profile annotation' is vague jargon that an agent may not decode without knowledge of XFN.

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?

There is no guidance on when to use this tool versus the other link tools, no prerequisites, and no statement about what happens with invalid tokens. The usage context (XFN rel attributes on hyperlinks) is only implied by the vocabulary name.

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.