Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

get_top_non_compliant_controls_detail

Retrieve controls with low compliance scores or non-compliant status for a given period, including details on assigned users, priority, and score.

Instructions

Function overview: Fetch control with low compliant score or non compliant controls. Arguments:

  1. period: Compliance period which denotes quarter of the year whose dashboard data is needed. By default: Q1 2024.

  2. count:

  3. page: If the user asks of next page use smartly decide the page.

Returns:

  • controls (List[NonCompliantControlVO]): A list of non-compliant controls.

    • name (str): Name of the control.

    • lastAssignedTo (List[UserVO]): List of users to whom the control was last assigned.

      • emailid (str): Email ID of the assigned user.

    • score (float): Score assigned to the control.

    • priority (str): Priority level of the control.

  • error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodYes
countNo
pageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
controlsNo
errorNo

Implementation Reference

  • The API endpoint constant URL_CCF_DASHBOARD_CONTROL_DETAILS = '/v2/aggregator/ccf-dashboard-control-details' used by the handler to make the API call.
    URL_CCF_DASHBOARD_CONTROL_DETAILS = "/v2/aggregator/ccf-dashboard-control-details"
  • Documentation/help entry listing the tool signature and description for users: 'get_top_non_compliant_controls_detail(period, count="1", page="1") - Get non-compliant controls'.
    • get_top_non_compliant_controls_detail(period, count="1", page="1") - Get non-compliant controls
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the function overview and return structure but lacks details on side effects, authentication, rate limits, or what happens with pagination beyond a vague note about 'smartly decide the page.'

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?

The description is structured with sections but is somewhat verbose and includes unclear phrasing like 'If the user asks of next page use smartly decide the page.' It could be more concise and directly informative.

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?

The description includes a detailed return structure, complementing the output schema. However, it lacks information on error handling, prerequisites, or typical usage scenarios, making it moderately complete.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning for 'period' (compliance quarter) but for 'count' only provides the field name, and for 'page' gives a vague instruction. Overall, it provides some but insufficient detail.

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 explicitly states the tool fetches controls with low compliant scores or non-compliant controls, which is specific. However, it does not differentiate from similar sibling tools like 'fetch_controls' or 'get_top_over_due_controls_detail', so clarity is slightly reduced.

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. The description does not mention prerequisites or when not to use, which is a significant gap given the many sibling tools for fetching controls.

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