Skip to main content
Glama

NexArt MCP Server

nexart_verify_consequential_cer

Read-onlyIdempotent

Verify inline consequential CER integrity. Producer identity and reported actions are not authenticated.

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_consequential_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.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description then adds a genuinely non-obvious caveat that producer identity and reported actions are NOT authenticated, which materially affects how an agent should interpret a successful result. It still omits what 'integrity' concretely covers and how failures 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.

Conciseness5/5

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

Two short sentences, action first and the trust caveat second, with no redundant or filler wording. Every sentence contributes information the agent needs.

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?

An output schema exists, so return-value explanation is unnecessary, and the single parameter is fully documented in the schema. What remains missing is the scope of the check itself and how this verifier differs from its five verify_* siblings, which is a real gap for a verification tool an agent must choose between.

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.'), so the schema already carries the semantics. The description adds no further detail about the bundle's expected format or size, making 3 the baseline.

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 consequential CER integrity'), plus a scope qualifier ('inline') that hints at the difference from lookup-style siblings. It does not, however, distinguish itself from the other verify_* siblings such as nexart_verify_ai_cer or nexart_verify_governed_execution, so an agent must guess which verifier applies.

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 word 'inline' implies the artifact is supplied in the request rather than fetched, which implicitly routes away from the lookup tools, and 'consequential' implies a class of CER. No explicit when-to-use, when-not-to-use, or prerequisite statement is given, so guidance remains inferred.

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