Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_available_control_actions

Retrieve available control actions for an assessment to confirm and execute the intended operation.

Instructions

This tool should be used for handling control-related actions such as create, update, or to retrieve available actions for a given control.

If no control details are given use the tool "fetch_controls" to get the control details.

  1. Fetch the available actions.

  2. Prompt the user to confirm the intended action.

  3. Once confirmed, use the execute_action tool with the appropriate parameters to carry out the operation.

Args:

  • assessmentName (str): Name of the assessment (required)

  • controlNumber (str): Identifier for the control (required)

  • controlAlias (str): Alias of the control (required)

If the above arguments are not available:

  • Use the fetch_controls tool to retrieve control details.

  • Then generate and execute a query to fetch the related assessment information before proceeding.

Returns: - actions (List[ActionsVO]): List of actions - actionName (str): Action name. - actionDescription (str): Action description. - actionSpecID (str): Action specific id. - actionBindingID (str): Action binding id. - target (str): Target. - error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assessmentNameYes
controlNumberNo
controlAliasNo
evidenceNameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalRecordsNo
compliantRecordsNo
nonCompliantRecordsNo
notDeterminedRecordsNo
recordsNo
Behavior3/5

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

No annotations, but description mentions retrieval and lists output fields. Does not disclose side effects, permissions, or error conditions beyond the error field.

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?

Description is somewhat lengthy with step-by-step instructions that could be separate. Front-loaded with purpose but includes redundant agent instructions.

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 return values and provides a workflow but lacks parameter descriptions and has inaccuracies. EvidenceName parameter not addressed.

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?

Description lists three args as required (contradicting schema where only assessmentName is required) and omits evidenceName. No explanation of what each parameter does beyond its name.

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?

The description clearly states it retrieves available actions for a control, matching the tool name. It distinguishes from sibling tools like fetch_controls and execute_action.

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 guidance: use fetch_controls if control details missing, prompt user, then use execute_action. However, it does not explicitly state when not to use.

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