Skip to main content
Glama

BRAINIAC Product Safety & Recalls

Parse a GS1 Digital Link URI

product-safety_gs1-digital-link-parse
Read-onlyIdempotent

Parse an uncompressed GS1 Digital Link URI into primary key, qualifiers and attributes; return canonical URI and element string. Price $0.01 USDC. POST /api/v1/product-safety/gs1-digital-link-parse. An unpaid call returns the x402 payment terms and does not run.

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": {
      "uri": "<uri>"
    },
    "name": "product-safety_gs1-digital-link-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYesuri, string, length 8 to 2048. Required.

Output Schema

NameRequiredDescriptionDefault
validNovalid. Boolean.
errorsNoerrors. Array.
sourcesNosources. Array.
attributesNoattributes. Array.
primaryKeyNoprimaryKey. Object.
qualifiersNoqualifiers. Array.
otherParamsNootherParams. Object.
canonicalUriNocanonicalUri. String.
elementStringNoelementString. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely new context: a $0.01 USDC price and the important failure mode that an unpaid call returns x402 payment terms and does not execute, which prevents an agent from misreading a payment-terms response as a parse result. Rate limits and error responses for invalid URIs remain unstated.

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?

Purpose is front-loaded in the first clause, followed by outputs and then the payment/endpoint metadata; no filler sentences. The semicolon-chained phrasing makes it slightly dense, but every clause carries information an agent needs.

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

Completeness4/5

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

An output schema exists, so the description need not detail return values, yet it helpfully names the parsed components. Combined with the payment gate and the read-only annotations, the definition covers what is needed to call the tool, with only malformed-URI handling left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented, so the baseline is 3. The description still adds meaningful input constraint by specifying that the URI must be an uncompressed GS1 Digital Link, narrowing what the agent should pass beyond the schema's mere length bounds.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (parse) and resource (an uncompressed GS1 Digital Link URI) and enumerates the outputs: primary key, qualifiers, attributes, canonical URI, and element string. This is clearly distinct from the sibling recall/alert search tools, which retrieve records rather than decode identifiers.

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 'uncompressed' qualifier implicitly tells the agent this tool will not handle compressed Digital Link URIs, and the payment note implies the call must be funded. There is no explicit when-to-use statement, no named alternative, and no guidance on what to do with a malformed or compressed URI.

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