Skip to main content
Glama

get_statement_import_status

Read-only

Check 'Did my statement finish importing?' for at most five jobs. Returns status and authenticated review link. Extraction isn't saved; read/save jobs may overlap, so counts aren't statement totals. No job found doesn't prove no import; older non-job imports are excluded. Read-only: never uploads, parses, saves, retries, or recovers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_statement_import_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientEmailNoAccountants: accepted client email only.

Output Schema

NameRequiredDescriptionDefault
linksYes
statusYes
importsYes
successYes
limitationsYes
availabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedOutput schema / properties / imports / items / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / imports / items / properties
      Removed value: -{
      -  "counts": {
      -    "additionalProperties": {
      -      "minimum": 0,
      -      "type": "integer"
      -    },
      -    "description": "Optional job-phase counts; keys vary by phase.",
      -    "type": [
      -      "object",
      -      "null"
      -    ]
      -  },
      -  "createdAt": {
      -    "format": "date-time",
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "phase": {
      -    "enum": [
      -      "save",
      -      "extraction",
      -      "unknown"
      -    ],
      -    "type": "string"
      -  },
      -  "state": {
      -    "enum": [
      -      "unknown",
      -      "uploaded",
      -      "awaiting_upload",
      -      "extracting",
      -      "review_ready",
      -      "partial",
      -      "saving",
      -      "saved",
      -      "saved_with_held",
      -      "saved_with_review",
      -      "failed"
      -    ],
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / imports / items / required
      Removed value: -[
      -  "phase",
      -  "state",
      -  "createdAt",
      -  "counts"
      -]
    • removedOutput schema / properties / imports / maxItems
      Removed value: -5
    • removedOutput schema / properties / links / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / links / properties
      Removed value: -{
      -  "review": {
      -    "format": "uri",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / links / required
      Removed value: -[
      -  "review"
      -]
    • removedOutput schema / properties / status / enum
      Removed value: -[
      -  "unknown",
      -  "empty",
      -  "mixed",
      -  "uploaded",
      -  "awaiting_upload",
      -  "extracting",
      -  "review_ready",
      -  "saving",
      -  "saved",
      -  "saved_with_held",
      -  "saved_with_review",
      -  "failed"
      -]
  2. Changed1 schema field changed
    • changedInput schema / properties / clientEmail / description
      Previous value: -"Accepted client's account email (accountants only)."New value: +"Accountants: accepted client email only."
  3. Changed1 schema field changed
    • changedInput schema / properties / clientEmail / description
      Previous value: -"Client account email. Accountants may use this only for an accepted ExpenseBot client."New value: +"Accepted client's account email (accountants only)."
  4. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly and non-destructive annotations, the description enumerates what the tool will never do (upload, parse, save, retry, recover) and discloses two non-obvious behaviors: extraction is not saved and read/save jobs may overlap so counts are not totals. It also flags the important negative-result caveat that 'no job found' does not prove no import occurred.

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?

The description is dense and front-loads the core question and return shape before the caveats, with no filler sentences. Phrasing is telegraphic in places ('Extraction isn't saved'), which trades a little readability for compactness.

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?

Given an output schema exists and annotations already cover the safety profile, nothing an agent needs to call this correctly is missing: the scope limit, the meaning of results, the unreliability of an empty result, and the side-effect guarantees are all stated.

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?

The single clientEmail parameter is fully documented in the schema, including the note that it applies to accountants acting on behalf of a client. The description adds nothing further about the parameter, which is acceptable given the 100% schema coverage but is not extra value.

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 gives a concrete operation framed as a question ('Did my statement finish importing?') plus two concrete outputs (status and authenticated review link), which is far more specific than the tool name alone. It scopes the work to 'at most five jobs' and to statement-import job types, which separates it in spirit from sibling status tools, though it never names an alternative for other kinds of imports.

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 establishes clear context for use (checking whether a statement import completed) and warns about the boundaries of that answer: counts are not statement totals and older non-job imports are excluded. It stops short of explicitly routing the agent elsewhere when the job predates the job system, so the alternative for that case is left 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.