LLPRO Campus

What LLPRO Certified means, how a product is assessed, and the public signed register. Nothing is certified yet

certified_lookup

Read-onlyIdempotent

LLPRO Certified public register lookup. Send a subject id (a product, service or agent id, lowercase letters, digits, . _ : -, up to 96 characters) to get issued, not_found, revoked or expired for it; send nothing to get the whole register (counts, head hash, criteria hash and the events, up to 200). Every answer is signed by LLPRO Certified (Ed25519 over canonical JSON); check it offline with the verifier at https://llpro.ai/certified-verify. At launch the register holds 0 issued: nothing is certified until a real assessment passes all written criteria. It does not show that a product is safe, legal or fit for any purpose, and not_found does not mean a product failed an assessment. Free. No network, no model, nothing about you is stored on disk.

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": "certified_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`subject`	No	Subject id to look up. Leave out to get the whole signed register.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark this read-only, idempotent, and closed-world, and the description still adds substantial context: every response is Ed25519-signed over canonical JSON, an offline verifier URL is given, the operation is free, uses no network or model, writes nothing to disk, and the register currently holds zero issued entries. It also pre-empts a likely misinterpretation by stating not_found does not mean a product failed assessment.

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 action, then the two modes, then the signature guarantee and caveats — a sensible information order. It is dense with semicolons and slightly redundant, since 'nothing is certified yet' appears in the title, the description body, and the zero-count note.

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

Completeness5/5

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

There is no output schema, so the description carries the return-shape burden and does so: status values, register contents (counts, head hash, criteria hash, up to 200 events), and the signing scheme. For a single-optional-parameter read tool, nothing needed to call it or interpret results is missing.

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 schema already explains leaving the subject out, but the description adds real value with the allowed character set (lowercase letters, digits, . _ : -) and the resulting status vocabulary (issued, not_found, revoked, expired). It goes beyond the schema rather than repeating it.

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?

Opens with a specific verb and resource: 'LLPRO Certified public register lookup.' The two calling modes are spelled out precisely — send a subject id for a per-subject status, send nothing for the whole register — so an agent knows exactly what resource is being retrieved and at what granularity.

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?

Explicitly states the two usage modes and what each returns, which is the main branch decision for a one-parameter lookup. It does not name an alternative tool or state when another lookup (e.g. a related register tool) would be preferable, so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LLPRO Campus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?