Skip to main content
Glama

Save evidence to a Ubi project

import_evidence
Destructive

Save a supplied v1.0 evidence envelope as an immutable project asset with provenance. Requires an explicit save request; URLs in the envelope are never fetched.

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": {
      "project_id": "<project_id>",
      "bundle": "<bundle>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "import_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleYes
filenameNopublic-evidence.json
project_idYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Adds real context beyond the annotations: the stored asset is immutable, provenance is recorded, and URLs inside the envelope are never fetched (consistent with openWorldHint=false). It does not explain why destructiveHint=true applies to an apparently additive save, nor what side effects the write has.

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 tight sentences, with the core action stated first and the two non-obvious constraints (explicit request, no URL fetching) following. No wasted wording.

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

Completeness3/5

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

For a mutating, non-idempotent-flagged write with a nested payload and no schema documentation, the description leaves the envelope structure and idempotency behavior unexplained, and the destructive/idempotent annotation signals go unaddressed. Output shape is covered by the output schema, so that omission is acceptable.

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, including a free-form nested 'bundle' object. The description only gestures at the bundle ('v1.0 evidence envelope', 'URLs in the envelope') and never explains project_id, filename, or the role of idempotency_key, so it does not compensate for the coverage gap.

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 and resource: saving a 'supplied v1.0 evidence envelope' as an 'immutable project asset with provenance.' That is concrete enough for an agent to recognize it as the write-side counterpart to asset-reading siblings, though no sibling is named to sharpen the distinction.

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?

'Requires an explicit save request' implies this is not an automatic side effect of some earlier step, which is useful framing, but there are no explicit when-to-use/when-not-to-use conditions and no named alternative (e.g., upload_text_asset for non-evidence uploads).

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