Skip to main content
Glama
eludden35

HIPAA Guardian MCP Server

getPrivacyPolicyPoints

Generate HIPAA-compliant privacy policy requirements for healthcare applications by analyzing data handling practices and identifying necessary security measures.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaYes

Implementation Reference

  • The handler function for the 'getPrivacyPolicyPoints' tool. It returns a structured text response containing a checklist of essential sections and topics to include in a privacy policy.
        async () => {
            return {
                content: [{
                    type: 'text',
                    text: `
    # Key Topics for a Privacy Policy
    
    This is a guide to help structure a privacy policy. You must consult with legal counsel to draft the final document.
    
    1.  **What Information We Collect:**
        * Explicitly list the types of data you collect (e.g., email address, name, IP address, usage data).
        * Distinguish between data the user provides directly and data you collect automatically.
    2.  **How We Use Your Information:**
        * Explain the purpose for collecting the data (e.g., to provide the service, for marketing, for analytics).
    3.  **How We Share Your Information:**
        * List the categories of third parties with whom you share data (e.g., cloud providers, analytics services, payment processors).
        * Explain the circumstances under which you might share data (e.g., with user consent, for legal reasons).
    4.  **Data Security:**
        * Briefly describe the measures you take to protect user data (e.g., encryption, access controls).
    5.  **Data Retention:**
        * Explain how long you keep user data and your policy for deleting it.
    6.  **Your Rights and Choices:**
        * Detail the rights users have regarding their data (e.g., right to access, right to delete, right to opt-out of marketing).
    7.  **Contact Information:**
        * Provide a clear way for users to contact you with privacy-related questions.
    8.  **Policy Updates:**
        * Explain how you will notify users of changes to the privacy policy.
    `
                }]
            };
        }
  • The schema definition for the 'getPrivacyPolicyPoints' tool, including description and an empty input schema (z.object({})) indicating no input parameters are required.
    {
        description: 'Provides a checklist of key sections and topics that should be included in a user-facing privacy policy. This is for guidance only and is not legal advice.',
        schema: z.object({}),
    },
  • server.ts:328-365 (registration)
    The registration of the 'getPrivacyPolicyPoints' tool using server.tool(), including schema and inline handler implementation.
    server.tool(
        'getPrivacyPolicyPoints',
        {
            description: 'Provides a checklist of key sections and topics that should be included in a user-facing privacy policy. This is for guidance only and is not legal advice.',
            schema: z.object({}),
        },
        async () => {
            return {
                content: [{
                    type: 'text',
                    text: `
    # Key Topics for a Privacy Policy
    
    This is a guide to help structure a privacy policy. You must consult with legal counsel to draft the final document.
    
    1.  **What Information We Collect:**
        * Explicitly list the types of data you collect (e.g., email address, name, IP address, usage data).
        * Distinguish between data the user provides directly and data you collect automatically.
    2.  **How We Use Your Information:**
        * Explain the purpose for collecting the data (e.g., to provide the service, for marketing, for analytics).
    3.  **How We Share Your Information:**
        * List the categories of third parties with whom you share data (e.g., cloud providers, analytics services, payment processors).
        * Explain the circumstances under which you might share data (e.g., with user consent, for legal reasons).
    4.  **Data Security:**
        * Briefly describe the measures you take to protect user data (e.g., encryption, access controls).
    5.  **Data Retention:**
        * Explain how long you keep user data and your policy for deleting it.
    6.  **Your Rights and Choices:**
        * Detail the rights users have regarding their data (e.g., right to access, right to delete, right to opt-out of marketing).
    7.  **Contact Information:**
        * Provide a clear way for users to contact you with privacy-related questions.
    8.  **Policy Updates:**
        * Explain how you will notify users of changes to the privacy policy.
    `
                }]
            };
        }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/eludden35/hipaa-guardian-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server