Skip to main content
Glama

evidence_add

Record evidence tied to a position with an optional stance—supports, opposes, or complicates—to keep strategy decisions traceable.

Instructions

Note something observed that bears on a position; optional stance: supports | opposes | complicates.

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": {
      "position_id": "<position_id>",
      "summary": "<summary>"
    },
    "name": "evidence_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNonote
stanceNo
summaryYes
position_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 behavioral burden. It discloses the meaning of the stance values (supports/opposes/complicates), which is genuinely useful, but says nothing about what persists, whether the position must already exist, permissions, or whether entries can be edited/removed later. For a write tool with zero annotation coverage this is a significant gap.

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 compact sentence with the core behavior front-loaded and no filler. It is efficient, though the terseness borders on under-specification given the undocumented parameters.

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 with 4 parameters at 0% schema coverage and no annotations, the description should do more. It leaves source and position_id semantics and the mutation's side effects unclear.

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%, so the description must explain the four parameters, but it only clarifies one: stance and its three allowed values. The 'source' parameter (with its 'note' default), 'summary', and 'position_id' remain undocumented anywhere.

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 verb 'Note' plus 'something observed that bears on a position' conveys that this records an evidence item attached to a position (position_id). It is specific enough to distinguish from generic siblings like 'add' or 'show', though the phrasing is slightly abstract rather than saying plainly 'add evidence to a position'.

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?

No when-to-use or when-not-to-use guidance is present, and no alternative is named even though a sibling called 'add' exists and could be confused with this. The only implicit guidance is that stance is optional.

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