QuickBooks Online MCP Server

get_employee

Retrieve a QuickBooks Online employee by ID to view or verify their details, enabling reliable lookups when you have only the employee identifier.

Instructions

Get an employee by Id from QuickBooks Online.

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": {
      "params": "<params>"
    },
    "name": "get_employee"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3/5.0

Behavior2/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 of behavioral disclosure. 'Get' implies a read-only lookup, but the description does not mention permission requirements, behavior when the ID is missing or inactive, or any other operational constraints.

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 a single front-loaded sentence with no filler. It is concise and structurally clear, even though it could carry more detail for completeness.

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

Completeness2/5

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

For a simple one-parameter lookup, the description is not complete enough: it omits when to use search_employees, error behavior for unknown IDs, and any indication of what an employee record includes. With no annotations and no output schema, those gaps are left entirely to inference.

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?

Schema description coverage is 0%, so the input schema documents only that a required string 'id' exists. The description adds that this is an employee ID in QuickBooks Online, but it does not explain ID format, expected values, or the nested 'params' wrapper.

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

Purpose4/5

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

The description states a specific verb ('Get'), resource ('employee'), and lookup condition ('by Id'), and names QuickBooks Online as the source. It does not explicitly differentiate from sibling tools such as search_employees, create_employee, update_employee, or delete_employee, so it falls short of a 5.

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 phrase 'by Id' implies the tool should be used when an employee ID is already known, which is a minimal contextual cue. It does not explicitly say when to choose search_employees instead, nor does it state exclusions or prerequisites, leaving the alternative implicit.

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

Deploy Server