Skip to main content
Glama

WritersLogic business agents

open-badges-verifier

Open Badges 2.0 / 3.0 credential verifier — Verifies an Open Badges credential end to end and says what could and could not be confirmed. Accepts an Open Badges 3.0 credential (JSON with an eddsa-jcs-2022 proof, or a VC-JWT signed with EdDSA, ES256 or RS256), an Open Badges 2.0 assertion (hosted, or signed as an RS256 JWS), a hosted-assertion URL, or a baked PNG or SVG image. Checks the 2.0/3.0 required fields, the issuance and expiry windo

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open-badges-verifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
jwsNoA compact JWS: an Open Badges 3.0 VC-JWT or an Open Badges 2.0 signed assertion.
urlNohttps URL of a hosted Open Badges 2.0 assertion or a hosted 3.0 credential.
imageNoA baked badge image, base64 (data URLs accepted): a PNG with an openbadges iTXt chunk, or an SVG with an openbadges:assertion or openbadges:credential element. Up to 6 MB decoded.
credentialNoThe credential or assertion as a JSON object (or the same as a JSON string, or a compact JWS string).
recipientIdentityNoOptional: the recipient's email or other identity to compare against the badge's recipient, including salted sha256$ and md5$ hashes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does useful work by saying the tool reports 'what could and could not be confirmed', signalling partial/qualified results rather than a bare boolean, and by implying a read-only check. But it never states that hosted URLs and images require network retrieval, whether anything is cached or written, or how failure modes are surfaced.

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?

Front-loaded with the standard and the verb, then a dense enumeration of accepted formats — appropriate for a format-dispatch tool. The prose is one long run-on sentence that appears truncated mid-clause ('the issuance and expiry windo'), which slightly hurts readability but wastes little space.

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 has five optional parameters, zero required, no annotations, and no output schema, so the description is the only place an agent can learn the calling contract. It explains formats and checks well, but never states that exactly one of jws/url/image/credential must be supplied, nor does it explain what the verification report contains. The truncated ending leaves the described checks incomplete.

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%, so the baseline is 3, but the description adds meaning by mapping formats to parameters: JWS vs. hosted URL vs. baked image vs. JSON object. It also adds the accepted signature algorithms (EdDSA, ES256, RS256) and hash forms (sha256$, md5$) that tell the agent which inputs will actually verify. What it does not clarify is the mutual exclusivity of the five optional inputs.

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 and resource — verifies an Open Badges 2.0/3.0 credential end to end — and immediately enumerates the exact input forms accepted (3.0 JSON with eddsa-jcs-2022 proof, VC-JWT, 2.0 hosted or RS256 JWS assertion, hosted URL, baked PNG/SVG). No sibling verifier in the list handles this standard, so the agent can distinguish it on the resource alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The enumeration of accepted input shapes effectively tells an agent when this tool applies: if you hold a baked image, a hosted URL, a compact JWS, or a JSON credential, this is the tool. What is missing is any exclusion or routing — nothing says what to do when the input is a non-Open-Badges credential or when partial verification is acceptable, and no alternative verifier is named.

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