Skip to main content
Glama

add_evidence

Store raw logs, error output, command results, and config verbatim as case evidence without paraphrasing or trimming; returns the evidence number for later reference.

Instructions

Store raw material VERBATIM as evidence: logs, error output, command results, config. Do not paraphrase or trim. Returns the evidence number.

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

Input Schema

NameRequiredDescriptionDefault
textYes
clientNo
case_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add real behavioral content — the stored payload is preserved verbatim with no normalization, and the call yields an evidence number — but omits what happens if case_id is invalid or unopened, any size/rate limits, or whether entries are mutable afterward.

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?

Three short sentences, front-loaded with the action and the strongest constraint (verbatim storage) before the return note. Little waste; the final sentence partially duplicates the output schema but is brief enough not to distract.

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?

An output schema exists, so the return value needs no elaboration, and the core storage contract is clear for a simple three-parameter tool. The unaddressed 'case_id'/'client' semantics and absent preconditions (does the case need to be open?) leave gaps an agent would have to resolve by trial.

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 three parameters, so the description must compensate. It meaningfully constrains 'text' (raw, unedited artifacts such as logs and command output) but says nothing about 'case_id' (presumably the owning case) or 'client' (undefined optional field), leaving two of three parameters opaque.

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 ('Store raw material ... as evidence') and enumerates the content classes (logs, error output, command results, config), which is much more concrete than the tool name alone. It does not distinguish itself from the sibling 'add_evidence_file', leaving the agent to guess which entry point applies to files vs. inline text.

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: 'Do not paraphrase or trim' tells the agent how to invoke it correctly, which is useful operational guidance. However, there is no explicit when-to-use vs. when-not, and neither 'add_evidence_file' nor 'search_evidence' is referenced, so the choice among the evidence tools rests on inference.

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