Skip to main content
Glama

NexArt MCP Server

nexart_verify_node_receipt

Read-onlyIdempotent

Verify a CER receipt Ed25519 signature with the published SDK. Signature, binding, lifecycle and server-pinned trust are separate; Project receipts are unsupported.

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": {
      "source": "<source>",
      "certificateHash": "<certificateHash>"
    },
    "name": "nexart_verify_node_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
receiptNo
certificateHashYes
signatureB64UrlNo

Output Schema

NameRequiredDescriptionDefault
sdkYes
keyStatusYes
signatureYes
reasonCodeYes
hashBindingYes
limitationsYes
signerTrustYes
keyLifecycleYes
nodeIdentityYes
lifecycleCodeYes
contractVersionYes
artifactIntegrityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile and the possibility of external access are known without the text. The description adds that verification runs through the published SDK and that trust dimensions are decomposed, but it never explains what an open-world call actually does (e.g. fetching a certificate) or what a failed verification yields.

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 dense sentences with no filler; the core action is front-loaded and the scope caveats follow. Every clause carries information an agent can act on.

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

Completeness2/5

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

For a four-parameter verification tool with zero schema descriptions, the definition is too thin: the source enum that determines whether an inline receipt or a public lookup is used is completely unexplained. The existence of an output schema relieves it of describing return values, but the input-side gap remains the dominant risk to a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description carries the full burden and largely drops it. It mentions 'Signature' and 'receipt', which loosely hint at signatureB64Url and receipt, but says nothing about the consequential source enum (inline vs public_lookup), certificateHash format, or why only two of the four parameters are required.

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 gives a specific verb and resource (verify a CER receipt Ed25519 signature) plus a named implementation detail (the published SDK). It also scopes the tool by declaring 'Project receipts are unsupported', which steers an agent away from nexart_verify_project_bundle, though it never names a sibling directly.

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?

There is a clear exclusion ('Project receipts are unsupported') and the statement that signature, binding, lifecycle and server-pinned trust are separate signals implies this tool handles only the signature layer. What is missing is an explicit pointer to which sibling covers those other layers, so the agent must infer the routing from names.

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