Skip to main content
Glama

NexArt MCP Server

nexart_lookup_cer

Read-onlyIdempotent

Look up one exact public NexArt hash. Return safe summaries and local returned-bundle integrity, not raw evidence or attestation authenticity.

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

Input Schema

NameRequiredDescriptionDefault
certificateHashYes

Output Schema

NameRequiredDescriptionDefault
sdkYes
familyYes
lookupYes
integrityYes
reasonCodeYes
limitationsYes
signerTrustYes
nodeSignatureYes
integrityScopeYes
receiptPresentYes
contractVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 open-world, so the safety profile is covered. The description adds real value beyond them by scoping the response: summaries and locally computed bundle integrity only, with no raw evidence and no attestation authenticity claim — a meaningful limit an agent must know before relying on the output.

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, zero filler, with the retrieval scope front-loaded and the output caveat immediately after. Nothing could be removed without losing information.

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?

A simple one-parameter lookup with an output schema and full annotation coverage needs little prose, and this definition covers scope and output limits. It omits what happens for a hash not found or not public, and doesn't indicate whether the lookup hits a local store or the network, which is a minor residual gap.

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

Parameters4/5

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

Only one parameter with 0% schema description coverage, but the description still adds meaning over the regex: "exact" excludes prefix or fuzzy matching and "public" restricts to public artifacts. The sha256 format itself is already enforced by the schema pattern, so nothing critical is missing.

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?

Uses a specific verb ("Look up") with a precise resource ("one exact public NexArt hash") and bounds the result to "safe summaries and local returned-bundle integrity." The explicit disclaimer "not raw evidence or attestation authenticity" implicitly separates it from the verify_* siblings, though no sibling is named outright.

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 "exact" signals this is a single-key retrieval rather than a search, and the closing clause tells the agent what the tool will not answer. However, it never states when to prefer it over nexart_verify_ai_cer or nexart_verify_project_bundle, leaving the routing to inference.

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