Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

add_check_to_asset

Add compliance checks to assets by creating new controls under parent controls. Enables structured governance and monitoring by linking specific requirements to individual assets.

Instructions

Add a new control and a new check to an asset under a specified parent control. The check will be attached to newly created control beneath the parent control.

Args: - assetId (str): Asset id. - parentControlId (str): Parent control id under which the check will be added. - checkName (str): Name of the check to be added. - checkDescription (str): Description of the check to be added.

Returns: - success (bool): Indicates if the check was added successfully. - error (Optional[str]): An error message if any issues occurred during the addition.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdYes
parentControlIdYes
checkNameYes
checkDescriptionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Describes the creation behavior and return structure (success boolean, error message), but lacks critical details about error conditions, idempotency, or atomicity since no annotations are provided.

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

Conciseness5/5

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

Well-structured with clear Args/Returns sections; every sentence conveys necessary information without redundancy.

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?

Covers basic inputs and outputs, but gaps remain regarding valid ID formats, constraint validation, and error scenarios given the tool's operational complexity.

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

Parameters4/5

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

Provides essential semantic meaning for all 4 parameters (e.g., clarifying parentControlId is the parent under which the check is added), compensating effectively for 0% schema description coverage.

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 (add control and check) and target resource (asset under parent control), but does not explicitly differentiate from sibling 'create_asset_and_check' which likely creates the asset itself.

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?

No guidance on when to use this tool versus alternatives like 'create_asset_and_check' or prerequisites for the asset/parent control existing.

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