Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_dashboard_framework_summary

Retrieve compliance framework dashboard summaries by period to view control assignments, track compliance status, and monitor due dates for audit reporting.

Instructions

Function Overview: CCF Dashboard Summary Retrieval

This function returns a summary dashboard for a specified compliance period and Common Control Framework (CCF). It is designed to provide a high-level view of control statuses within a given framework and period, making it useful for compliance tracking, reporting, and audits.

Args:

  • period:
    The compliance quarter for which the dashboard data is requested.
    Format: "Q1 2024"

  • framework_name:
    The name of the Common Control Framework whose data is to be retrieved.

Dashboard Overview

The dashboard provides a consolidated view of all controls under the specified framework and period. It includes key information such as assignment status, compliance progress, due dates, and risk scoring to help stakeholders monitor and manage compliance posture.

Returns: - controls (List[FramworkControlVO]): A list of framework controls. - name (str): Name of the control. - assignedTo (str): Email ID of the user the control is assigned to. - assignmentStatus (str): Status of the control assignment. - complianceStatus (str): Compliance status of the control. - dueDate (str): Due date for completing the control. - score (float): Score assigned to the control. - priority (str): Priority level of the control. - page (int): Current page number in the overall result set. - totalPage (int): Total number of pages. - totalItems (int): Total number of items. - error (Optional[str]): An error message if any issues occurred during retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodYes
framework_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
controlsNo
pageNo
totalPageNo
totalItemsNo
errorNo
Behavior4/5

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

Discloses pagination behavior (page/totalPage), error handling patterns, and dashboard content details (risk scoring, due dates) that go beyond the empty annotations.

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?

Well-structured with clear headers, but unnecessarily verbose due to the detailed Returns section which duplicates information already present in the output schema.

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?

Comprehensive coverage of the tool's functionality and data contents given the simple 2-parameter input schema; adequately complete despite not addressing similar dashboard tools.

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

Parameters5/5

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

Excellent compensation for 0% schema description coverage by providing detailed semantic meaning for both parameters, including the period format example ('Q1 2024') and framework identification.

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 retrieves a summary dashboard for a CCF and compliance period with specific use cases (tracking, reporting, audits), though it doesn't explicitly differentiate from similar siblings like fetch_dashboard_framework_controls.

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 context on when it's useful (compliance tracking, audits) but lacks explicit guidance on when not to use it or which sibling tools to use instead for detailed vs. summary data.

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