intakeq-mcp

get_form

Retrieve a single intake form submission by ID from IntakeQ. Every call is audit-logged for PHI protection.

Instructions

Get a single intake form submission by ID. PHI — every call is audit-logged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "form_id": "<form_id>"
    },
    "name": "get_form"
  }
}

Input Schema

Name	Required	Description	Default
`form_id`	Yes	The IntakeQ intake form ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 7, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses that the data is PHI and every call is audit-logged, which is a meaningful behavioral trait beyond the schema, especially because no annotations are provided. It does not detail error handling or response structure, but the audit-log warning adds valuable context.

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

Conciseness5/5

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

The description is two sentences: the first states the core purpose, the second a critical caution. Every word earns its place, and the key information is front-loaded.

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?

For a one-parameter getter with no output schema, the description covers the essential purpose and a key behavioral trait. It could mention that the return value is the full form submission, but the wording 'Get a single intake form submission' makes that implicit. Overall, it is reasonably complete.

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

Parameters3/5

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

The input schema already describes form_id as 'The IntakeQ intake form ID' (100% coverage). The tool description only restates 'by ID' without adding new semantic detail, so the baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the action (Get), the resource (a single intake form submission), and the identifier (by ID). It distinguishes from sibling tools like list_intake_forms (list vs single) and get_note (different resource).

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?

The usage is implied: 'Get a single intake form submission by ID' suggests using this when you have a specific form ID. However, it does not explicitly contrast with alternatives such as list_intake_forms for discovering IDs or mention 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.