Skip to main content
Glama

NexArt MCP Server

nexart_verify_ai_cer

Read-onlyIdempotent

Verify inline AI CER V1/V2 integrity using the NexArt SDK. No signature, signer-trust or completeness claim.

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": {
      "bundle": "<bundle>"
    },
    "name": "nexart_verify_ai_cer"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleYesAn inline NexArt artifact. No URLs, paths, credentials or openings.

Output Schema

NameRequiredDescriptionDefault
sdkYes
toolYes
checksYes
familyYes
protocolYes
reasonCodeYes
limitationsYes
recordVersionYes
contractVersionYes
artifactIntegrityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 closed-world, so the safety profile is covered. The description adds real value beyond that by bounding the verification claim: it verifies integrity only, not signatures, signer trust, or completeness — a limit an agent could otherwise over-trust. It stops short of describing failure/output semantics.

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?

Two short sentences, no filler, with the positive scope front-loaded and the caveat second. 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 return values need no explanation, and the tool's single-parameter surface is fully documented in the schema. The description covers purpose and claim boundaries adequately; only the positive when-to-use routing against the sibling verification tools is missing.

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?

There is a single parameter with 100% schema description coverage ('An inline NexArt artifact. No URLs, paths, credentials or openings.'). The description's word 'inline' reinforces the schema constraint, but adds no new meaning about the bundle format or expected structure, so the schema does the work.

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?

States a specific verb ('Verify') and a specific resource ('inline AI CER V1/V2 integrity'), and names the engine ('NexArt SDK'). It implicitly separates itself from the consequential/project-bundle verification siblings by scoping to AI CER, though it never names them explicitly.

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 description gives useful negative scope ('No signature, signer-trust or completeness claim'), which tells an agent what this tool will not answer. However, it never states a positive call condition or points to the sibling to use when signature or signer-trust checks are needed, so routing must be inferred from the name alone.

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