Skip to main content
Glama

NexArt MCP Server

nexart_verify_project_bundle

Read-onlyIdempotent

Verify an inline Project Bundle and embedded AI CERs using the SDK; require project hash integrity.

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_project_bundle"
  }
}

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.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world verification operation. The description adds that the bundle is inline, uses the SDK, and requires project hash integrity, but it does not explain failure behavior, permission requirements, or what verification checks are performed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is a single front-loaded sentence with no redundant wording. It is dense with domain jargon such as 'AI CERs' and 'SDK', but appropriately sized for the tool.

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?

For a one-parameter verification tool with rich annotations and an output schema, the description covers the essential scope: inline bundle verification, embedded AI CERs, and hash integrity. The main missing element is explicit routing guidance versus sibling verification tools.

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?

The schema describes the single bundle parameter as an inline NexArt artifact with no URLs, paths, credentials, or openings. The tool description adds useful meaning by clarifying that this is a Project Bundle with embedded AI CERs and that project hash integrity is part of the expected artifact.

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 states a specific verb and resource: verify an inline Project Bundle, including embedded AI CERs and project hash integrity. This distinguishes it from lookup siblings and from the standalone CER verification tools, though it does not explicitly name an alternative.

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 by 'inline Project Bundle' and 'require project hash integrity', suggesting this tool is for in-memory bundle verification rather than URL/path-based lookup. However, there is no explicit when-to-use versus when-not-to-use guidance or named sibling alternative.

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