Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Find data event recovery infos

find_data_event_recovery_infos
Read-onlyIdempotent

You can use the DataEventRecoveryInfoQuery request to find out whether data event recovery information exists for the given subscriber. If it does, then data events have been lost and need to be recovered. (Note that there will be no data event recovery information to return if TrackLostEvents was “tleNone” in the subscriber’s DataEventSubscriptionAdd request.)

Returns the v2 request to send, and the webhook payload QuickBooks' answer arrives in (this operation's response_json: its data shape and the status codes to handle).

Possible errors (error.code / error.type; the call result explains each): 1030 unsupported_request, 3150 missing_element, 3210 invalid_value, 3220 not_authorized, 3231 request_not_processed, 3250 feature_not_enabled, 3260 insufficient_permission, 3261 personal_data_access_denied, 3262 payroll_subscription_required, 3264 merchant_services_subscription_required

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": {
      "subscriber_id": "<subscriber_id>"
    },
    "name": "find_data_event_recovery_infos"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idNoYour own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
subscriber_idYesA unique identifier that an application sets when it adds a subscription so that the application can later query or delete the subscription.

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
queryYesThe query parameters: the arguments you passed.
methodYes
headersYesSend with the request. Resent unchanged when no 201 came back, it answers with the request already queued.
webhookYesJSON Schema of the payload POSTed to webhook_url once QuickBooks answers, with this operation's response_json (data shape and status codes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the bar is lower; the description still adds real value by disclosing the two-step mechanics (a v2 request is returned to send, and the answer arrives via webhook in response_json) and by enumerating the error codes/types the caller must handle. It stops short of describing pagination or result volume, which keeps it from a 5.

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

Conciseness3/5

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

The purpose is front-loaded in the first sentence, which is good, but the block is dense: a long nested parenthetical plus a twelve-code error enumeration consume substantial space and mix typographic quotes and formatting. The error list has value but is presented as a run-on rather than structured content.

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?

Given an output schema exists, the description needn't detail return shapes, yet it usefully explains the webhook/response_json delivery model and the error taxonomy an agent must anticipate. What remains unclear is only the practical call sequence for handling the webhook answer, a minor gap for a read-only query tool.

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?

Schema description coverage is 100%, so the schema already documents request_id, include_qbxml, and subscriber_id in detail. The description only refers to 'the given subscriber' and adds no format, syntax, or edge-case meaning beyond the schema, so the baseline 3 applies.

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 and resource: query whether DataEventRecoveryInfo exists for a given subscriber, and explains the semantic meaning of a hit (data events were lost and must be recovered). It does not explicitly contrast with the sibling delete_data_event_recovery_info, 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?

Usage is implied by the framing 'You can use the DataEventRecoveryInfoQuery request to find out whether...', and the parenthetical adds a useful negative condition (no info is returned when TrackLostEvents was 'tleNone'). However, there is no explicit statement of when to choose this over alternatives such as the delete counterpart, so guidance remains implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources