Skip to main content
Glama

aio

by org.aioq

Register a model for Tier 0 measurement

register_for_certification

Register a model for AIO Tier 0 measurement. Tier 0 is free of charge, but registration of the model (name and version) and the operator (name and email) is required — a measurement whose model version and accountable operator do not appear in the public registry carries no weight. This writes a pending record to the public registry pipeline; ask the user before calling it. Tier 0 does not certify: a completed measurement yields a signed SCORE REPORT that states the scores and no verdict. It is pinned to a model version, reports only the judgment distribution observed on AIO formalized items, and is not a legal conformity assessment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNameYesModel name, e.g. "example-model".
operatorUrlNoOptional http(s) URL of the operator.
modelVersionYesModel version or release date. The measurement is pinned to it.
operatorNameYesThe organization accountable for operating the model.
operatorEmailYesContact email of the operator. Used for the registration record and notifications.

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond annotations. It discloses that the tool 'writes a pending record to the public registry pipeline' (a mutation, consistent with readOnlyHint=false), emphasizes the need to ask the user, and explains the nature of the result (signed score report, no verdict). This adds significant behavioral context beyond the generic annotations.

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?

The description is a single focused paragraph of three sentences. Every sentence carries essential information: the registration requirement, the pending-write behavior with user-consent instruction, and the non-certification caveats. There is no filler or redundancy.

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?

For a registration tool with no output schema and relatively low annotation richness, the description covers all critical aspects: what it does, why registration matters (registry weight), the pending nature, the user-consent requirement, what Tier 0 does/doesn't provide, and the scope of the score report. This is comprehensive for the tool's complexity.

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 description coverage is 100%—every parameter has a detailed description. The tool description mentions 'model (name and version)' and 'operator (name and email),' but this only restates what the schema already conveys. It adds no extra parameter-level semantics, so the baseline score of 3 applies.

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?

The description clearly states the action ('Register a model') and the target (AIO Tier 0 measurement), and it explicitly distinguishes this from certification with 'Tier 0 does not certify.' The title reinforces the purpose, and the description is specific enough to differentiate from sibling tools like verify_certification.

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 description provides clear context: registration is required for a measurement to carry weight, and it instructs 'ask the user before calling it.' It implicitly tells you when not to use it (not for certification or legal conformity) but does not explicitly name alternative tools, so it stops short of fully explicit alternatives.

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

All aio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: fetching items vs. distributions, listing vs. fetching specific entities, and distinct submission endpoints for benchmark, eval, and RFC comments. Even the two 'get items' tools (bench vs. eval) are clearly differentiated by their descriptions and use cases.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores. Verbs are grouped by action type (get_, list_, submit_, start_, register_, verify_, search_), and the patterns are predictable and uniform across the set.

Tool Count4/5

At 17 tools, the set is slightly above the ideal 3-15 range but each tool serves a distinct purpose. The breadth of the domain (papers, RFCs, standards packs, benchmarks, evaluation, certification, vocabulary, search) justifies the count, and no tool feels redundant.

Completeness4/5

The tool surface covers the major workflows: listing and fetching resources, starting and submitting evaluation attempts, registering and verifying certifications, and submitting benchmark/RFC responses. Minor gaps exist, such as no direct tool to cancel an evaluation attempt or list a specific benchmark run by id, but these are edge cases and the core lifecycle is well-covered.

Resources