Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_automated_controls_of_an_assessment

Retrieve automated controls for a specific assessment ID to verify compliance status, monitor activation state, and review associated audit rules.

Instructions

To fetch the only the automated controls for a given assessment. If assessment_id is not provided use other tools to get the assessment and its id.

Args: - assessment_id (str, required): Assessment id or plan id.

Returns: - controls (List[AutomatedControlVO]): List of controls - id (str): Control ID. - displayable (str): Displayable name or label. - alias (str): Alias of the control. - activationStatus (str): Activation status. - ruleName (str): Associated rule name. - assessmentId (str): Assessment identifier. - error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assessment_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
controlsNo
errorNo
Behavior2/5

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

No annotations provided; description adds no information about side effects, rate limits, or execution behavior beyond basic input handling.

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?

Structured with Args/Returns sections, but contains typo in opening line and redundant Returns documentation given output schema exists.

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?

Adequate for a single-parameter tool; detailed return value documentation is redundant given output schema exists but doesn't detract significantly.

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?

Adds semantic meaning ('Assessment id or plan id') but contradicts schema: description labels assessment_id as 'required' while schema marks it optional (default: '', required parameters: 0).

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 fetches 'automated controls' (distinguishing from general fetch_controls sibling), though has typo 'the only the'.

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

Usage Guidelines3/5

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

Provides fallback guidance if assessment_id is missing, but lacks explicit differentiation from sibling control-fetching tools like fetch_leaf_controls_of_an_assessment.

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