Skip to main content
Glama

Build a modified EUI-64 identifier

bpj_modified_eui64
Read-onlyIdempotent

Insert FFFE and invert the universal bit of a six-octet MAC to form an IPv6 interface ID.

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": {
      "value": "<value>"
    },
    "name": "bpj_modified_eui64"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, repeatable, local computation. The description contributes the actual transformation rule, which is genuine behavioral content. It does not say what the returned value looks like (plain hex vs. colon-separated octets) or how malformed input is handled, and with no output schema that remains undisclosed.

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 sentence that front-loads the operation and ends with the output type. Every clause carries information; there is no filler or restatement of the title.

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 tool is simple (one param, no output schema, annotations supplied), and annotations plus the one-sentence explanation cover safety and intent. The missing pieces are the input string format and the output representation, both of which an agent needs to call it correctly and interpret the result, and neither schema nor annotations supply them.

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 coverage is 0% and the single parameter is only labeled 'Input value' with maxLength 240, so the description must carry the semantics. It does imply the value is a six-octet MAC, which is real added meaning. It does not specify the expected textual form (colon-, hyphen-separated, or bare hex) or whether a leading 02/00 universal bit matters, so the format ambiguity survives.

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 the exact operation ('Insert FFFE and invert the universal bit') and the input/output pair (six-octet MAC -> IPv6 interface ID). That is a specific verb+resource, far beyond the bare tool name. It stops short of a 5 because it does not distinguish itself from any other identifier-shaping tool (e.g. bpj_dq_identifier_shape) or state its scope relative to them.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. Usage is only implied: an agent infers this is the tool for converting a MAC to an EUI-64-based interface ID from the algorithm described. For a single-purpose pure transform that implication is fairly strong, but it is inference rather than guidance.

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.