Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_resources_by_check_name_summary

Retrieve compliance summaries for check resources by check name, asset run ID, and resource type. Returns total, compliant, and non-compliant counts to assess compliance status efficiently without retrieving full resource lists.

Instructions

Use this to get the summary on check resources Use this when total items in 'fetch_resources_for_check' is high Get check resources summary for given asset run id, resource type and check Paginated data is enough for summary Get a summarized view of check resources based on - Compliance breakdown for resources - Total Resources available - Total compliant resources - Total non-compliant resources

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

Returns: - complianceSummary (dict): Summary of compliance status across checks. - error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
resourceTypeYes
checkYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
complianceSummaryNo
errorNo
Behavior3/5

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

Describes what the summary contains (compliance breakdown) and that paginated data suffices, but lacks details on rate limits, caching, or side effects (no annotations provided to contradict).

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?

Redundant opening ('Use this to get...' followed by 'Get...'), but uses structured Args/Returns sections; bullet points for compliance breakdown are effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequately describes return values despite output schema existing, but incomplete due to missing `check` parameter documentation and no mention of error handling beyond Returns section.

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

Parameters2/5

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

Schema has 0% description coverage, but description only compensates for 2 of 3 parameters (missing `check` parameter documentation in Args section).

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 action (get summary) and resource (check resources), and distinguishes from sibling `fetch_resources_for_check` by specifying use case for high item counts.

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

Usage Guidelines4/5

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

Explicitly states when to use ('when total items in fetch_resources_for_check is high') and implies when not to use (when you need full details vs summary).

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