Skip to main content
Glama

Inspect a UUID

bpj_inspect_uuid
Read-onlyIdempotent

Read the version nibble, variant bits, and Nil or Max forms from a UUID.

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": {
      "uuid": "<uuid>"
    },
    "name": "bpj_inspect_uuid"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful behavioral detail of which components are reported (version nibble, variant bits, Nil/Max forms), but is silent on error behavior for malformed input and on any output shape, despite there being no output schema.

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 sentence with no filler, and the extracted facets are front-loaded. Nothing is wasted, though the terseness leaves little room for the missing guidance noted 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 inspector the description is roughly adequate, and it partly substitutes for the absent output schema by naming what is returned. However, with no output schema and an undocumented input parameter, the lack of accepted-format and invalid-input behavior leaves real gaps.

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?

There is a single required parameter with 0% schema description coverage; the schema only supplies a title ("Hyphenated UUID") and maxLength 36. The description does not clarify accepted input forms (braces, urn:uuid: prefix, uppercase, unhyphenated 32-char), so it does little to compensate for the coverage gap.

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 ("Read") and resource (UUID) plus the exact facets extracted: version nibble, variant bits, and Nil/Max forms. An agent immediately knows this is structural UUID introspection. It does not differentiate from the similarly-named 'inspect'-style siblings (bpj_text_inspect, bpj_inspect_import_map), so it stops short of a 5.

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 only implied: an agent can infer this is for when you need version/variant/edge-case form info about a UUID. There is no explicit statement of when to use it versus parsing the UUID yourself, and no mention of prerequisites or exclusions.

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.