Skip to main content
Glama

Import Evidence Bundle

import_evidence_bundle
Idempotent

Imports a JSON evidence bundle from an absolute local path, validates evidence IDs and manifests, then atomically merges it as non-executed data.

Instructions

Read the JSON bundle at the supplied local path, validate every Evidence ID and canonical manifest, then atomically merge it. Imported content is data only and is never executed.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "/tmp/evidence.json"
    },
    "name": "import_evidence_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute local filesystem path for the evidence bundle to import; relative paths are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose the write profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false). The description adds meaningful context beyond them: validation of every Evidence ID and canonical manifest, atomic merge semantics, and that imported content is data-only and never executed. It still omits what happens when validation fails and whether existing content is replaced or combined.

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?

A single tight sentence that front-loads the read/validate/merge sequence with no wasted wording. Slightly dense but every clause carries 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?

For a one-parameter tool with no output schema, the description covers the key behaviors an agent needs: validation, atomicity, and the no-execution safety guarantee. Only failure behavior and merge-vs-replace semantics are left unclear.

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?

Schema description coverage is 100% and there is a single required parameter whose absolute-path constraint is fully documented in the schema. The description repeats the local-path idea without adding format or size details, so baseline 3 is appropriate.

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 chain and resource: read the JSON bundle at the local path, validate Evidence IDs and canonical manifest, then atomically merge. That is far more informative than the title, though it does not name a sibling such as export_evidence_bundle or import_managed_reconstruction to delimit scope.

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 only implied by the name and the path requirement; the description never says when to pick this over export_evidence_bundle or import_managed_reconstruction. An agent can infer it imports from a local file rather than a managed source, but no explicit guidance or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools