Skip to main content
Glama

build_soc2_evidence

Generates a SOC 2 evidence binder mapped to AICPA Trust Service Criteria from receipts, with evidence counts and coverage metrics, and returns Markdown for audit kickoff.

Instructions

Build a SOC 2 evidence binder mapped to AICPA Trust Service Criteria (2017) — security (CC1-CC9), availability (A1), processing integrity (PI1), confidentiality (C1), privacy (P-series). Each criterion gets a receipt-derived evidence count + days-of-coverage metric. Returns Markdown to walk into the audit kickoff with.

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": {
      "scope": "<scope>",
      "receipts": "<receipts>"
    },
    "name": "build_soc2_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYesSoc2Scope: organizationName, auditPeriodStart, auditPeriodEnd, inScope (categories), serviceAuditor, servicesDescription.
receiptsYesVAOS receipts.
controlOwnersNoOptional map of criterion id → control owner string (for RACI).
coverageThresholdDaysNoDays-of-coverage threshold below which a criterion is flagged as a gap. Default 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It usefully discloses the output form ('Returns Markdown') and that metrics are 'receipt-derived', suggesting a pure computation rather than a persisted artifact, but it never states whether anything is written anywhere, what happens when receipts are sparse, or any prerequisite validation — meaningful gaps for a four-param builder.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the resource and framework version, then the per-criterion output contract, then the intended use. No filler or restated title.

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 complex tool with nested objects (Soc2Scope, receipts) and no output schema, the description adequately conveys structure and return format. A gap remains around required input shape for 'receipts' and behavior when coverage data is missing, but the essentials for correct invocation are present.

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 four parameters including the 30-day default on coverageThresholdDays. The description adds conceptual color ('receipt-derived evidence count', 'days-of-coverage metric') but does not explain controlOwners or how scope.inScope interacts with the criterion set, so it adds little beyond 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+resource ('Build a SOC 2 evidence binder') and pins the exact mapping target (AICPA Trust Service Criteria 2017, with CC1-CC9, A1, PI1, C1, P-series enumerated). This clearly separates it from framework siblings like build_iso_42001, build_nist_ai_rmf, and build_gdpr_dpia without needing to name them.

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 closing phrase 'walk into the audit kickoff with' implies the audit-preparation scenario, but there is no explicit when-to-use/when-not guidance and no routing to sibling builders (e.g., use build_gdpr_dpia for privacy-rule audits). Usage is only implied.

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