Skip to main content
Glama

Attify

Get an evidence record

get_evidence
Read-onlyIdempotent

One evidence record of the public sample by its id (ev_…): the outcome, the failed check, the evidence tier, the redacted excerpt, quoted as customer text, and why it failed.

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": {
      "evidence_id": "<evidence_id>"
    },
    "name": "get_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
evidence_idYese.g. "ev_a669881efdac".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add content. It does: it scopes results to 'the public sample' and flags that the excerpt is redacted and rendered as customer-quoted text, which are non-obvious behavioral facts. It does not say what happens when an id is not found.

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 dense sentence with the resource and key front-loaded and no filler. It is slightly list-heavy and lacks an explicit verb, 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 read with no output schema, enumerating the returned fields and noting redaction is close to sufficient. The remaining gap is error/not-found behavior, which matters for an id-based lookup.

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 coverage is 100% and the parameter already carries a format example, so the schema does the heavy lifting. The description only restates the id-prefix convention ('ev_…') without adding constraints such as case sensitivity or accepted id sources.

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?

Names a specific resource ('one evidence record') and the lookup key ('by its id (ev_…)'), and enumerates what the record contains (outcome, failed check, tier, redacted excerpt, failure reason). It does not explicitly contrast with siblings like list_findings or explain_check, so it stops short of 5.

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?

The phrase 'by its id (ev_…)' implies this is a direct single-record lookup once you already hold an evidence id, but there is no explicit when-to-use/when-not guidance and no named alternative for browsing or searching evidence.

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