Skip to main content
Glama

Get security evidence

get_security_evidence
Read-only

Read where the organisation's compliance evidence is delivered and how each delivery went. report picks it: destinations (Vanta, Wazuh or webhook receivers; whether a credential is configured, never the credential, and an endpoint only by its host; the twin of ankra security evidence destinations list) or deliveries (each month's evidence for a framework sent to a destination, newest first, with its status, attempts and receipt; the twin of ankra security evidence deliveries list). Needs security.read; a caller confined to one project is refused, since the evidence is the whole organisation's. Read-only: creating a destination, sending and submitting a delivery are not offered here.

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": {
      "report": "<report>"
    },
    "name": "get_security_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNodeliveries: rows to return, 1 to 100 (default 100).
reportYesWhich listing to read.
destination_idNodeliveries: only this destination's (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only provide readOnlyHint, and the description adds substantial context beyond that: the required security.read scope, the fact that project-scoped callers are rejected because evidence is organisation-wide, that credentials are reported as configured/not without exposing them, that endpoints are returned by host only, and that deliveries are ordered newest first.

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?

Front-loaded with the read purpose, then branches cleanly into the two `report` modes, then constraints. The long parentheticals carrying CLI-equivalence references are dense and slightly heavy, but each sentence supplies information the agent needs; nothing is filler.

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?

With no output schema, the description does the work of describing returned content — provider, credential-configured flag, endpoint host for destinations; month/framework, status, attempts and receipt for deliveries. That is good coverage for a read-only three-parameter tool, though it stops short of describing pagination or exact response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining that `report` selects between two distinct result shapes and thereby governs how `limit` and `destination_id` apply. The per-parameter constraints themselves (1-100 range, UUID format) are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Read where the organisation's compliance evidence is delivered and how each delivery went") and immediately disambiguates the two modes the single tool covers via the `report` parameter. An agent can tell exactly what is read and how the two listings differ without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit exclusions ("creating a destination, sending and submitting a delivery are not offered here") and access conditions ("Needs security.read"; project-confined callers are refused), which tells the agent when the call will fail. It does not name sibling MCP tools as alternatives, only the equivalent CLI commands, so routing guidance to other server tools is left implicit.

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.