Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_resources_by_check_name

Retrieve resources for specific compliance checks using asset run ID and check name. Returns resource details, types, and compliance status with pagination support for large datasets.

Instructions

Get resources for given asset run id, and check name. 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 10 to 50.

If the resource 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 resource.

  1. Call fetch_resources_for_check 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: Asset run id. - checkName: Check name.

Returns: - resources (List[ResourceVO]): A list of resources. - name (str): Name of the resource. - resourceType (str): Type of the resource. - complianceStatus (str): Compliance status of the resource. - error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
checkNameYes
pageNo
pageSizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourcesNo
pageNo
totalPageNo
totalItemsNo
errorNo
Behavior5/5

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

Discloses timeout risks, pagination requirements, and recommends increasing pageSize from 10 to 50 on retries—critical behavioral context absent from 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?

Content is valuable but verbose, mixing narrative instructions with docstring-style Args/Returns sections that duplicate the output schema; could be front-loaded better.

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?

Complete for the tool's complexity, covering pagination workflow and sibling alternatives, though unnecessarily duplicative of the output schema in the Returns section.

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?

Compensates for 0% schema description coverage by mapping parameter names to basic meanings (Asset run id, Check name), but lacks domain context on what constitutes valid IDs or check names.

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 it retrieves resources by asset run ID and check name, and explicitly distinguishes itself from the sibling 'summary tool' for large datasets.

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?

Provides explicit step-by-step pagination workflow, timeout retry logic, and clear guidance on when to use the alternative summary tool instead.

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