Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_checks

Retrieve detailed compliance checks for specific asset runs and resource types. Access check rules, compliance status, and priority levels with built-in pagination for large datasets.

Instructions

Get checks for given assets run id and resource type. Use this function to get all checks for given assets run id and resource type Use 'fetch_assets_summary' tool to get asset run id Use 'fetch_resource_types' tool to get all resource types Function accepts page number (page) and page size (pageSize) for pagination. If MCP client host unable to handle large response use page and pageSize. If the request times out retry with pagination, increasing pageSize from 5 to 10.

If the check data set is large to fetch efficiently or results in timeouts, it is recommended to use the 'summary tool' instead to get a summarized view of the checks.

  1. Call fetch_checks with page=1, pageSize=10

  2. Note the totalPages from the response

  3. Continue calling each page until complete

  4. Summarize all results together

Args: - id (str): Asset run id - resourceType (str): Resource type - complianceStatus (str): Compliance status

Returns: - checks (List[CheckVO]): A list of checks. - name (str): Name of the check. - description (str): Description of the check. - rule (RuleVO): Rule associated with the check. - type (str): Type of the rule. - name (str): Name of the rule. - activationStatus (str): Activation status of the check. - priority (str): Priority level of the check. - complianceStatus (str): Compliance status of the check. - compliancePCT (float): Compliance percentage. - error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
resourceTypeYes
pageNo
pageSizeNo
complianceStatusNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
checksNo
pageNo
totalPageNo
totalItemsNo
errorNo
Behavior4/5

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

No annotations provided; description compensates with timeout/retry behavior, pagination strategy, and performance guidance (when to use summary instead), though omits rate limits or auth requirements.

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?

Contains redundancy (first two sentences restate each other) and unnecessarily detailed Returns section (output schema exists), though pagination instructions are well-structured.

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 for a paginated fetch tool: covers prerequisite data acquisition, pagination mechanics, timeout mitigation, and alternative tools; no critical gaps given the complexity.

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?

With 0% schema coverage, description partially compensates: explains id/resourceType via sibling references and page/pageSize functionally, but complianceStatus is tautological (just 'Compliance status') and page/pageSize omitted from Args block.

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 specific verb (get) and resource (checks) and distinguishes from siblings by referencing fetch_checks_summary for large datasets and fetch_assets_summary/fetch_resource_types as prerequisites, though opening is slightly redundant.

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

Usage Guidelines5/5

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

Excellent explicit guidance: prerequisites (which tools to call first), when-not-to-use (large datasets → use summary tool), timeout handling, and step-by-step pagination workflow.

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