Skip to main content
Glama

Annual report as PDF

firmafakta_annual_report
Read-only

Buy a company's annual report from Bolagsverket for one fiscal year, as one PDF with the audit report and the other documents filed for that year. Give org_number and fiscal_year_end, which firmafakta_lookup lists among the company's annual reports. Answers with a link to the PDF that opens once and expires: give it to the user to open, do not open it yourself, or the purchase is used up. Costs the report price in credits (see describe's prices); a fiscal year without a report is refused without charge.

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": {
      "org_number": "<org_number>",
      "fiscal_year_end": "<fiscal_year_end>"
    },
    "name": "firmafakta_annual_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_numberYesthe company's org number, ten digits, with or without hyphen
fiscal_year_endYesthe last day of the fiscal year, YYYY-MM-DD, as firmafakta_lookup lists it for the company's annual reports

Output Schema

NameRequiredDescriptionDefault
urlNothe PDF; it opens once, so give it to the user rather than open it
usageNo
expires_atNowhen the link stops working if not opened

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changed
    • removedOutput schema / properties / expires_at / type
      Removed value: -"string"
    • removedOutput schema / properties / url / type
      Removed value: -"string"
    • removedOutput schema / properties / usage / properties / credits_charged / maximum
      Removed value: -2147483647
    • removedOutput schema / properties / usage / properties / credits_charged / minimum
      Removed value: --2147483648
    • addedOutput schema / properties / usage / properties / credits_charged / title
      Added value: +"credits_charged"
    • removedOutput schema / properties / usage / properties / credits_charged / type
      Removed value: -"integer"
    • removedOutput schema / properties / usage / properties / credits_left / maximum
      Removed value: -2147483647
    • removedOutput schema / properties / usage / properties / credits_left / minimum
      Removed value: --2147483648
    • addedOutput schema / properties / usage / properties / credits_left / title
      Added value: +"credits_left"
    • removedOutput schema / properties / usage / properties / credits_left / type
      Removed value: -[
      -  "null",
      -  "integer"
      -]
    • removedOutput schema / properties / usage / properties / offer
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / usage / properties / plan / title
      Added value: +"plan"
    • removedOutput schema / properties / usage / properties / plan / type
      Removed value: -"string"
    • addedOutput schema / properties / usage / properties / refills_on / title
      Added value: +"refills_on"
    • removedOutput schema / properties / usage / properties / refills_on / type
      Removed value: -"string"
    • addedOutput schema / properties / usage / properties / throttled / properties / plan / title
      Added value: +"plan"
    • removedOutput schema / properties / usage / properties / throttled / properties / plan / type
      Removed value: -"string"
    • addedOutput schema / properties / usage / properties / throttled / properties / waited_ms / title
      Added value: +"waited_ms"
    • removedOutput schema / properties / usage / properties / throttled / properties / waited_ms / type
      Removed value: -"integer"
    • removedOutput schema / properties / usage / properties / throttled / required
      Removed value: -[
      -  "waited_ms",
      -  "plan"
      -]
    • addedOutput schema / properties / usage / properties / throttled / title
      Added value: +"throttled"
    • removedOutput schema / properties / usage / properties / throttled / type
      Removed value: -[
      -  "null",
      -  "object"
      -]
    • removedOutput schema / properties / usage / required
      Removed value: -[
      -  "plan",
      -  "credits_charged"
      -]
    • addedOutput schema / properties / usage / title
      Added value: +"usage"
    • removedOutput schema / properties / usage / type
      Removed value: -"object"
    • removedOutput schema / required
      Removed value: -[
      -  "url",
      -  "expires_at",
      -  "usage"
      -]
  2. Added

TDQS

A4.1/5.0
Behavior2/5

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

The description discloses rich behavior beyond the schema: a credit cost, a single-use expiring link, and a no-charge refusal for years without a report. However, it describes a purchase that deducts credits and consumes a one-time link, which is a state-changing side effect, while annotations declare readOnlyHint=true — the description contradicts that declaration, so the transparency score is penalized.

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?

Three dense sentences, front-loaded with the action and deliverables, then inputs, then the critical handling warning. No sentence is filler; the one risk clause ('do not open it yourself, or the purchase is used up') justifies its length.

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?

For a paid, non-idempotent operation with a one-shot output link, the description covers cost, failure behavior (refused without charge), input provenance, and how to handle the returned link. With an output schema present, it need not describe the return payload, so nothing material 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 already 100%, so the baseline is 3; the description adds meaning by tying fiscal_year_end to the values returned by firmafakta_lookup and by describing the answer as a PDF link, which helps the agent source inputs correctly. It adds no formatting detail beyond what the schema already states.

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 gives a specific verb and resource ('Buy a company's annual report from Bolagsverket for one fiscal year') and defines the deliverable ('one PDF with the audit report and the other documents filed for that year'). This is unmistakably distinct from siblings such as firmafakta_lookup (which lists reports) and firmafakta_fetch.

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?

It tells the agent where the inputs come from ('fiscal_year_end, which firmafakta_lookup lists among the company's annual reports') and gives explicit handling instructions for the result ('give it to the user to open, do not open it yourself, or the purchase is used up'). It does not state when the agent should not buy at all (e.g., prefer a free listing first), which keeps it from a 5.

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.