Skip to main content
Glama

evaluate_evidence_policy

Evaluate an evidence bundle against declarative compliance rules from evidence.policy.json or an inline policy to identify violations and confirm required controls.

Instructions

Evaluates an evidence bundle against declarative compliance rules defined in evidence.policy.json or an inline policy.

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": {
      "bundleId": "<bundleId>"
    },
    "name": "evaluate_evidence_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyNoInline policy definition overriding file on disk.
strictNoEnforce strict compliance (fail if any warnings exist).
bundleIdYesThe unique identifier of the evidence bundle to evaluate.
policyPathNoPath to evidence.policy.json file (defaults to workspace discovery).
workspacePathNoOptional workspace path hint to locate the bundle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

B3.1/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 and does not meet it. It never says whether the evaluation is read-only, what happens when rules are violated (error vs. returned violations), how 'strict' changes failure behavior, or how the policy file is discovered when policyPath is omitted.

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 front-loaded sentence with no filler, covering the resource and the two policy sources. It is efficient, though its brevity is partly the cause of the missing behavioral detail.

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?

The tool takes five parameters, including a nested free-form policy object, and has no output schema and no annotations. In that situation the description should explain the result shape (violations/warnings) and failure semantics, but it stops at restating the purpose.

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 description coverage is 100%, so the schema already documents all five parameters including policyPath defaults and the strict flag. The description only adds the high-level distinction between file-based and inline policy, which is a marginal contribution over the structured data.

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+resource ('Evaluates an evidence bundle') plus the rule source ('evidence.policy.json or an inline policy'), so the operation is unambiguous. It does not differentiate from nearby siblings such as verify_evidence_bundle or check_bundle_quorum, whose names suggest overlapping verification semantics.

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 only implied by the purpose: an agent can infer this is the tool for rule-based compliance checks rather than cryptographic verification. There is no explicit when-to-use, when-not-to-use, or named alternative among the many verification siblings.

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