intakeq-mcp

list_practitioners

Retrieve all practitioners from your IntakeQ account to obtain valid PractitionerIds for scheduling appointments.

Instructions

List all practitioners in the IntakeQ account. Call this before create_appointment to find a valid PractitionerId.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_practitioners"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the operation lists all practitioners, implying a read-only, safe action. However, it does not mention authentication requirements, pagination, or output formatting, which would improve transparency.

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?

Two sentences, no redundancy. The first states the function, the second gives actionable usage guidance. Every word earns its place, and the most important info 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?

With no output schema or annotations, the description is the sole source of information. It clearly explains the purpose, usage timing, and how to use the output. It omits potential details like pagination or authentication, but for a simple list-all tool, the description is sufficient for most contextual needs.

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

Parameters5/5

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

There are zero parameters, so the baseline is 4. The description adds significant value by telling the agent that the response contains a valid PractitionerId, which is directly useful for the follow-up create_appointment call. This goes beyond the empty schema.

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?

Verb 'List' + resource 'practitioners' clearly states the operation. Scoping to 'IntakeQ account' and the explicit tie to 'find a valid PractitionerId' before create_appointment distinguishes this from sibling list tools (list_notes, list_clients, etc.).

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

Usage Guidelines4/5

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

Provides explicit usage context: 'Call this before create_appointment to find a valid PractitionerId.' This tells the agent exactly when to use it. It lacks explicit alternatives or when-not-to-use, but the scenario is very concrete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.