Skip to main content
Glama

Tokenbooks - crypto and fiat accounting and payments

Request Report Export

request_report_export

Queue a spreadsheet, PDF, or JSON accounting report—such as profit and loss, trial balance, balance sheet, journal, or transaction export—for a reporting period; track the returned requestId with get_request_status.

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": {
      "workspaceRef": "<workspaceRef>",
      "portfolioRef": "<portfolioRef>",
      "reportType": "<reportType>",
      "format": "<format>",
      "fromDate": "<fromDate>",
      "toDate": "<toDate>"
    },
    "name": "request_report_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYesExport format
toDateYesReport period end ISO timestamp
fromDateYesReport period start ISO timestamp
reportTypeYesReport type
totalsOnlyNoReturn summary only when true
portfolioRefYesPortfolio exact name or slug
workspaceRefYesWorkspace exact name or slug

Output Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "requestId": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "requestId"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false); the description adds important behavior beyond that — this tool queues an asynchronous job and returns a requestId that must be polled. It stops short of saying what happens on repeated requests (duplicate jobs) or what the request is scoped to.

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

Conciseness4/5

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

It is a single dense sentence with the core action front-loaded and the follow-up step placed at the end where it belongs. The em-dash example list is long but each item corresponds to a distinct report type the agent may need to recognize.

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 an output schema present, the description does not need to explain return values, and it appropriately covers the async workflow. For a 7-parameter job-creating tool it is nearly complete, with only the gaps around duplicate requests and permission/scope requirements remaining.

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 all seven parameters including both enums. The description's mention of formats and report examples merely restates the enum values rather than adding semantics such as date-range inclusivity, workspaceRef/portfolioRef resolution rules, or totalsOnly behavior.

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 uses a specific verb ('Queue') plus resource ('accounting report') and enumerates concrete report examples (profit and loss, trial balance, balance sheet, journal, transaction export) that map to the enum. It also implicitly distinguishes itself from the synchronous listing/detail siblings by framing the output as an async export job.

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?

It names the follow-up path explicitly ('track the returned requestId with get_request_status'), which is genuine routing value. However, it gives no guidance on when to prefer this async export over synchronous siblings like list_portfolio_transactions or get_journal_entry, and no prerequisites or exclusions are stated.

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