Skip to main content
Glama
diblaze

bokio-mcp

by diblaze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bokio_download_sie

Read-only

Download a fiscal year's raw SIE 4 export to a file, or retrieve the first 4,000 characters as text when no path is given. Use computed tools for balances, ledgers, VAT, and P&L.

Instructions

Download the raw SIE 4 export of one fiscal year to savePath, or return its first 4,000 characters as text when savePath is omitted. For balances, ledgers, VAT or profit and loss use the computed tools, which read this export themselves and do the arithmetic.

Input Schema

NameRequiredDescriptionDefault
savePathNoFile path inside BOKIO_DOWNLOAD_DIR, else the working directory; an existing file is never overwritten, so pick a new name.
companyIdNoBokio company id. Defaults to BOKIO_COMPANY_ID if omitted.
fiscalYearIdYesId from bokio_list_fiscal_years; an unknown id returns a not-found error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / fiscalYearId / description
      Added value: +"Id from bokio_list_fiscal_years; an unknown id returns a not-found error."
    • addedInput schema / properties / savePath / description
      Added value: +"File path inside BOKIO_DOWNLOAD_DIR, else the working directory; an existing file is never overwritten, so pick a new name."
  2. Addedv0.4.0

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true. The description adds real information the annotations don't cover: the 4,000-character truncation of text mode and the fact that the computed tools parse this same export. It does not discuss export size, encoding, or failure modes beyond the not-found error that the schema already lists.

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 with no filler. The primary mode and its fallback come first, and the routing advice to alternative tools comes second.

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

Completeness5/5

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

No output schema exists, yet the description fully explains what the agent gets back in both modes: a file at savePath, or the first 4,000 characters as text. Combined with 100% parameter coverage and the named sibling alternatives, nothing needed for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so 3 is the baseline. The description adds meaning the schema does not: omitting savePath changes the tool from file download to inline text, which is the single most consequential parameter behavior here. The remaining per-parameter details (dir precedence, overwrite protection, id source) are already in the 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?

States a specific verb and resource (download the raw SIE 4 export of one fiscal year) and describes both output modes: file when savePath is present, first 4,000 characters of text when omitted. It also separates itself from the family of computed tools that consume the same export.

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

Usage Guidelines5/5

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

Explicitly tells the agent that balances, ledgers, VAT, and profit and loss should go to the computed tools instead, naming the sibling categories and explaining why (those tools do the arithmetic on this export). The dual-mode condition is also stated outright.

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

Deploy Server

Other Tools