Caribooks (QuickBooks Online)

get exchange rate

get_exchange_rate

Read-only

Get the exchange rate QuickBooks uses for a currency into the company's home currency on a date (multicurrency companies only).

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": {
      "currency": "<currency>"
    },
    "name": "get_exchange_rate"
  }
}

Input Schema

Name	Required	Description
`company`	No	Which connected QuickBooks company to use (name, realm id, or connection id). Optional when only one company is connected.
`currency`	Yes	Source currency code, e.g. USD (the rate into the company's home currency).
`as_of_date`	No	YYYY-MM-DD; defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds that the rate is the one QuickBooks uses and is date-specific, which is useful context. However, it does not disclose behavior for non-multicurrency companies, missing rates, or the return shape, so it adds only modest behavioral transparency beyond the annotations.

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 that communicates the operation, direction, date dimension, and multicurrency restriction without any filler. Every phrase earns its place.

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 simple read-only lookup with fully documented parameters, the description plus schema covers the essential invocation details. The main gaps are the lack of an explicit pointer to search_exchange_rates for plural/search scenarios and no note about what happens if the company is not multicurrency.

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 coverage is 100%, and all three parameters already have meaningful descriptions: company, currency, and as_of_date. The description reinforces the currency/home-currency direction and date relevance, but it does not add significant semantic detail beyond what the schema already provides.

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: get the exchange rate QuickBooks uses for a source currency into the company's home currency on a date. It also adds the important scope restriction that this applies to multicurrency companies only. However, it does not explicitly distinguish itself from the sibling search_exchange_rates, so an agent might not immediately know when to use this getter versus the search tool.

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?

The description provides a clear precondition (multicurrency companies only) and defines the operation's context: one currency, home-currency direction, and a date. It does not name alternatives such as search_exchange_rates or explain when to prefer one over the other, so it stops short of full routing guidance.

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

All Caribooks (QuickBooks Online) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?