Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_evidence_records

Retrieve evidence records by ID with optional compliance status filtering to audit resources, track violations, and review detailed configuration data for governance.

Instructions

Get evidence records for a given evidence ID with optional compliance status filtering. Returns max 50 records but counts all records for the summary.

Args: - id (str): Evidence ID - compliantStatus Optional[(str)]: Compliance status to filter "COMPLIANT", "NON_COMPLIANT", "NOT_DETERMINED" (optional).

Returns: - totalRecords (int): Total records. - compliantRecords (int): Number of complian records. - nonCompliantRecords (int): Number of non compliant records. - notDeterminedRecords (int): Number of not determined records. - records (List[RecordListVO]): List of evidence records. - id (str): Record id. - name (str): System name. - source (str): Record source. - resourceId (str): Resource id. - resourceName (str): Resource name. - resourceType (str): Resource type. - complianceStatus (str): Compliance status. - complianceReason (str): Compliance reason. - createdAt (str): The date and time the record was initially created.
- otherInfo (Any): Additional information.
- error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
compliantStatusNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalRecordsNo
compliantRecordsNo
nonCompliantRecordsNo
notDeterminedRecordsNo
recordsNo
Behavior4/5

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

Discloses critical pagination behavior (max 50 records returned with full count in summary) and error handling that would typically appear in annotations.

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

Conciseness3/5

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

Well-structured with Args/Returns sections but unnecessarily verbose in documenting return values since an output schema exists.

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?

Comprehensive coverage of inputs and behavioral limits despite lack of annotations, though usage context against siblings is missing.

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

Parameters5/5

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

Fully compensates for 0% schema description coverage by defining parameter purposes (Evidence ID) and enumerating valid filter values for compliantStatus.

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?

Clearly states the tool retrieves evidence records by ID with optional filtering, though it doesn't explicitly differentiate from sibling evidence tools like fetch_evidence_record_schema.

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?

Provides no explicit guidance on when to use this tool versus alternatives such as fetch_evidence_available_actions or fetch_evidence_record_schema.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ComplianceCow/cow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server