Skip to main content
Glama

NexArt MCP Server

nexart_lookup_project_bundle

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": {
      "projectHash": "<projectHash>"
    },
    "name": "nexart_lookup_project_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectHashYes

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 cover read-only, idempotent, non-destructive and open-world behavior, so the bar is lower. The description still adds genuine value by scoping the return: safe summaries plus local bundle integrity, explicitly not raw evidence and not an authenticity verdict, which prevents the agent from treating output as a trust signal.

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. The retrieval scope comes first and the critical negative scoping ('not raw evidence or attestation authenticity') is placed immediately after, where it is most likely to be read.

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?

With an output schema present, return values need not be spelled out, and annotations carry the safety profile. The description covers retrieval scope and result limits adequately; only miss / not-found behavior and the point at which the agent should escalate to a verify tool are left unstated.

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?

Schema coverage is 0%, so the description must compensate. It does so partially: "one exact public NexArt hash" conveys that the hash must be complete (no prefix or fuzzy matching) and publicly addressable, which meaningfully qualifies the single projectHash parameter beyond the schema's regex pattern.

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 ("look up") and a precise resource ("one exact public NexArt hash"), and the phrase "one exact" signals single-item retrieval rather than a search. The closing clause hints that verification of attestation authenticity belongs to sibling tools, though it never names nexart_verify_project_bundle directly.

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?

Usage is implied rather than stated: the agent can infer this is the retrieval path and that verification of authenticity is out of scope, but there is no explicit 'use this when X, use nexart_verify_project_bundle when Y' routing. Against six similarly-named verify siblings, that omission leaves real ambiguity.

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