Skip to main content
Glama
eludden35

HIPAA Guardian MCP Server

getCoreDefinitions

Retrieve precise definitions for key HIPAA compliance terms including PHI, Business Associate, De-Identification, and Patient Rights to ensure accurate implementation of healthcare data regulations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schemaYes

Implementation Reference

  • server.ts:80-88 (handler)
    The handler function that implements the logic for the 'getCoreDefinitions' tool. It returns core HIPAA definitions from the hipaaData knowledge base as text content.
    async ({ term }) => {
      // Return the entire section as it contains all definitions contextually.
      return {
        content: [{
          type: 'text',
          text: `Here are the core definitions from the guide:\n\n${hipaaData['what_is_hipaa?']}`
        }]
      };
    }
  • Zod schema defining the input for the tool: an object with a 'term' field enum of specific HIPAA terms.
    schema: z.object({
      term: z.enum(['PHI', 'Business Associate', 'De-Identification', 'Patient Rights']),
    }),
  • server.ts:72-89 (registration)
    The server.tool call that registers the 'getCoreDefinitions' tool, providing name, description, schema, and handler function.
    server.tool(
      'getCoreDefinitions',
      {
        description: 'Provides foundational definitions for terms like PHI (Protected Health Information), Business Associate, and De-Identification.',
        schema: z.object({
          term: z.enum(['PHI', 'Business Associate', 'De-Identification', 'Patient Rights']),
        }),
      },
      async ({ term }) => {
        // Return the entire section as it contains all definitions contextually.
        return {
          content: [{
            type: 'text',
            text: `Here are the core definitions from the guide:\n\n${hipaaData['what_is_hipaa?']}`
          }]
        };
      }
    );
  • Loads the hipaaData JSON knowledge base at startup, which is used by the getCoreDefinitions handler to provide definitions.
    const knowledgeBasePath = path.join(process.cwd(), 'hipaa-content.json');
    let hipaaData;
    try {
      hipaaData = JSON.parse(fs.readFileSync(knowledgeBasePath, 'utf-8'));
      console.log('✅ HIPAA knowledge base loaded successfully');
    } catch (error) {
      console.error(`FATAL ERROR: Could not load knowledge base from ${knowledgeBasePath}.`);
      console.error('Please ensure the hipaa-content.json file exists in the same directory.');
      console.error('Error details:', error);
      process.exit(1); // Exit if the core data is missing
    }
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