Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

fetch_rule_design_notes

Retrieve or create design notes for a compliance rule, with options to modify or regenerate after reviewing existing content.

Instructions

Fetch and manage design notes for a rule.

WORKFLOW:

  1. CHECK EXISTING NOTES:

  • Always check if design notes exist for the rule first (whether user wants to create or view)

  • If found: Present complete notebook to user in readable format

  • If not found: Offer to create new ones

  1. IF NOTES EXIST:

  • Show complete notebook with all sections (this serves as the VIEW)

  • Ask: "Here are your design notes. Modify or regenerate?"

  1. USER OPTIONS:

  • MODIFY:

  1. Ask "Do you need any changes to the design notes?"

  2. If no changes needed: Get user confirmation, then call create_design_notes() to update

  3. If changes needed: Collect modifications, show preview, get confirmation, then call create_design_notes() to update

  • REGENERATE:

  1. Generate the design notes using generate_design_notes_preview()

  2. Show preview to user

  3. Get user confirmation

  4. If confirmed: Call create_design_notes() to save the regenerated design notes

  • CANCEL: End workflow

  1. IF NO NOTES EXIST:

  • Inform user no design notes found

  • Ask: "Create comprehensive design notes for this rule?"

  • If yes: Generate the design notes using generate_design_notes_preview()

  • Show preview to user

  • Get user confirmation

  • If confirmed: Call create_design_notes() to generate

KEY RULES:

  • MUST follow this workflow explicitly step by step

  • Always check for existing notes first whenever user asks about design notes (create or view)

  • ALWAYS get user confirmation before calling create_design_notes()

  • If any updates needed, explicitly call create_design_notes() tool to save changes

  • Present notes in Python notebook format

  • Use create_design_notes() for creation and updates

Args: rule_name: Name of the rule

Returns: Dict with success status, rule name, design notes content, and error details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rule_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description carries the burden. It describes a multi-step workflow that involves calling other tools, but doesn't clearly state that this tool itself only fetches data and relies on others for mutations. The side effects and dependencies are not transparent.

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?

The description is overly long (over 30 lines) with a detailed workflow that belongs in a separate guide rather than a tool description. It lacks conciseness and front-loading; the core purpose is buried.

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 covers the return dict format and workflow steps, but it mixes orchestration instructions with the tool's function. It is complete in the sense of detailing a process, but that process blurs the line between this tool and others, potentially leading to misuse.

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?

Only one parameter (rule_name) with 0% schema description coverage. The description merely restates 'Name of the rule' without adding meaningful context (e.g., format, case sensitivity, required source).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Fetch and manage design notes', which broadens the purpose beyond 'fetch'. It includes creation and update workflows, but the tool name suggests only fetching. This ambiguity makes it unclear whether this tool is a simple fetcher or a workflow orchestrator.

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 explicit guidance on when to use this tool versus alternatives like create_design_notes or generate_design_notes_preview. The workflow implies usage but doesn't state when not to use it.

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