Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

by ComplianceCow
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

fetch_resources_summary

Retrieve compliance summaries for resources by asset run ID and resource type. View total, compliant, and non-compliant counts to assess resource status without fetching high-volume detailed lists.

Instructions

Use this to get the summary on resource 
Use this when total items in 'fetch_resources' is high
Fetch a summary of resources for a given asset run id and resource type.
Get a summarized view of resources include
    - Compliance breakdown for resource
        - 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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
complianceSummaryNo
errorNo

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

Describes return structure (complianceSummary dict, error string) and summary contents, but lacks disclosure of side effects, rate limits, or caching behavior given no annotations exist.

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

Conciseness2/5

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

Contains redundancy between opening lines ('Use this to get...' vs 'Fetch a summary...'), fragmented sentences, and inconsistent indentation that reduces clarity.

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?

Adequately covers the simple 2-parameter input and output structure for a summary tool, including specific breakdown of what the compliance summary contains.

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?

Partially compensates for 0% schema coverage by clarifying 'id' is asset run ID, though 'resourceType' description is tautological and unhelpful.

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 (fetch summary) and resource (resources), and explicitly differentiates from sibling 'fetch_resources' by mentioning when to use it (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?

Provides explicit conditional guidance ('Use this when total items in fetch_resources is high') indicating when to prefer this over the sibling fetch_resources tool.

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