Skip to main content
Glama

Feature Library

Check versions, licences and the checklist

check
Read-only

Free. The rules version (its hash) and the catalogue version, the checks to run on the build before calling it done, the runnable checks (get_check) that prove the ones a checklist can’t, and, with a licence token, the account’s licences and the parts it owns. Pass evidence (what the checks returned, area by area) and it says whether the build may be called done, and what is missing.

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

Input Schema

NameRequiredDescriptionDefault
evidenceNoOptional, before calling a build done: { layout: [layoutProbe.steps/toggle results], rings: [layoutProbe.rings results], motion: { reducedMotion: true, how }, performance: { msPerUpdate, target }, placement: { widths: [1440, 375] } }. Only layout, rings and motion (they protect people) can fail a build; the rest is worth a look.
decisionsNoOptional: the library defaults this build broke, as design decisions: [{ rule, chose, why }]. The person’s wishes win over defaults; say why for each.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description adds real context beyond them: the call is free, licence-scoped data only appears when a licence token is supplied, and passing evidence changes the response from a listing into a pass/fail verdict gated on layout, rings and motion. It does not describe the verdict's shape or what happens when evidence is partial, but the added behavioral context is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single long run-on sentence stacked with parentheticals, opened by the fragment 'Free.' Every clause carries content, but the packing of versions, checklist, sibling routing and evidence verdict into one sentence makes it slow to parse and hurts front-loading of the primary use case.

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?

With no output schema, the description must carry the return-value burden, and it does enumerate the main returned items plus the verdict behavior. However, it leaves the verdict's format, the failure semantics when checks fail, and how licences are authorized (the token channel) under-specified, which matters for a tool that makes a 'may be called done' judgment.

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 coverage is 100%, so both evidence and decisions are documented in the schema, and the description only loosely restates evidence as 'what the checks returned, area by area'. Worth noting it implies a licence token input that is not in the schema at all, which is a small ambiguity rather than added parameter meaning.

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?

The description names concrete resources it surfaces (rules version hash, catalogue version, the checklist of checks, licences and owned parts with a licence token) and explicitly routes runnable checks to the sibling get_check. The verb is weaker than the resource list — 'check' merely restates the tool name — and the tool is a bundle of several distinct concerns, but an agent can still tell what it returns and how it differs from get_check.

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?

It gives clear usage context: call it to read rules/catalogue versions and the checklist, and pass evidence 'before calling a build done' to get a done/not-done verdict. It also names get_check as the place for runnable checks. There is no explicit when-not guidance or statement of ordering relative to the other siblings (get_brief, check_look).

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