Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

get_tasks_summary

Retrieve available compliance tasks with essential details for selection and automatically analyze output intentions to suggest follow-up tasks that ensure workflows produce actionable final deliverables.

Instructions

Resource containing minimal task information for initial selection.

This tool is also used as a fallback resource when fetch_tasks_suggestions is disabled or does not return suitable matches, ensuring the user always has access to a broader list of available tasks for manual selection.

This resource provides only the essential information needed for task selection:

  • Task name and display name

  • Brief description

  • Purpose and capabilities

  • Tags for categorization

  • Inputs/Outputs params with minimal details

  • Basic README summary

Use this for initial task discovery and selection. Detailed information can be retrieved later using tasks://details/{task_name} for selected tasks only.

AUTOMATIC OUTPUT ANALYSIS BY INTENTION:

  • MANDATORY: Analyze each task's output purpose and completion level during selection

  • IDENTIFY output intentions that require follow-up processing:

    • SPLITTING INTENTION: Outputs that divide data into separate categories → REQUIRE consolidation

    • EXTRACTION INTENTION: Outputs that pull raw data without formatting → REQUIRE transformation

    • VALIDATION INTENTION: Outputs that check compliance without final reporting → REQUIRE analysis/reporting

    • PROCESSING INTENTION: Outputs that transform data but don't create final deliverables → REQUIRE finalization

OUTPUT COMPLETION ASSESSMENT:

  • EVALUATE: Does this output serve as a final deliverable for end users?

  • ASSESS: Is this output consumable without additional processing?

  • DETERMINE: Does this output require combination with other outputs to be meaningful?

  • IDENTIFY: Is this output an intermediate step in a larger workflow?

WORKFLOW COMPLETION ENFORCEMENT:

  • NEVER present task selections that end with intermediate processing outputs

  • AUTOMATICALLY suggest tasks that fulfill incomplete intentions

  • ENSURE every workflow produces actionable final deliverables

  • RECOMMEND tasks that bridge gaps between current outputs and user goals

Mandatory functionality:

  • Retrieve a list of task summaries based on the user's request

  • Analyze task outputs and suggest additional tasks for workflow completion

  • If no matching task is found for the requested functionality, prompt user for confirmation

  • Based on user response, either proceed accordingly or create support ticket using create_support_ticket()

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Ambiguous whether the tool automatically performs output analysis and workflow completion enforcement, or if these are instructions for the agent; conflates tool behavior with agent responsibilities.

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

Conciseness2/5

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

Extremely verbose with redundant ALL CAPS sections that mix tool capabilities with agent instructions; significant bloat obscures the core purpose.

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?

Attempts to cover output handling and workflow implications given the output schema, but overreaches into prescriptive agent behavior rather than describing tool capabilities.

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?

Baseline score for zero parameters; description does not contradict the empty schema but implies filtering by 'user's request' which could cause confusion.

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 identifies the tool as providing minimal task information for initial discovery and distinguishes it from detailed retrieval via the tasks://details endpoint.

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?

Specifies use for initial selection and as a fallback when fetch_tasks_suggestions is disabled, but the extensive workflow enforcement sections blur the line between tool usage and agent post-processing instructions.

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