Skip to main content
Glama

upload_evidence

Store bounded text evidence with optional name, media type, and actor handle so agents can record provenance-tracked knowledge without filesystem paths.

Instructions

Store a bounded text evidence object; no filesystem paths.

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": {
      "text": "<text>"
    },
    "name": "upload_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
textYes
media_typeNotext/plain
actor_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and mostly does not meet it. "Bounded" hints at a size limit but never states it, and there is no mention of authentication, actor attribution, deduplication, overwrite behavior for the name field, or what happens on exceeding the bound.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, but that brevity comes at the cost of under-specification rather than efficiency. It is short without being dense with useful information.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but for a four-parameter write tool with zero annotation and zero schema-description coverage the description is far too thin. Key facts an agent needs to call it correctly, such as the size bound and the meaning of actor_handle and media_type, are absent.

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, so the description must compensate and largely fails. Only the word "text" implies that text is raw content rather than a path, and "no filesystem paths" clarifies that indirectly; name, media_type, and actor_handle are left entirely unexplained by both schema and description.

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 gives a specific verb ("Store") and resource ("bounded text evidence object") plus a scoping constraint ("no filesystem paths"). An agent can tell this is an evidence-ingestion tool rather than a lookup or mutation of agent state, though it never distinguishes itself from named siblings like record or submit_review.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling to prefer for related operations (e.g., record vs. submit_review vs. upload_evidence). The only guidance is the negative constraint on filesystem paths, which narrows inputs but not tool selection.

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