Skip to main content
Glama

List imports that can be undone

imports_list
Read-onlyIdempotent

List up to 10 recent imports that can still be undone, with IDs and member details, to locate an earlier import_commit ID for rollback.

Instructions

List the latest imports (up to 10, newest first) that import_undo can still take back, each with id, source, startedAt, inserted (expenses created) and importedByMemberId. Use it to find the importId of an import_commit from an earlier session; imports with settled shares are left out. Admins see all imports of the flat, other members only their own. Read-only. For the preview of new data use import_preview.

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": "imports_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds real context: the 10-item cap, newest-first ordering, omission of settled-share imports, and the admin-vs-member visibility split. Only the redundant 'Read-only.' sentence falls short of adding anything, keeping it from a 5.

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 scoping constraint leads and the sibling routing closes, with no filler sentences. The middle is a dense field enumeration that runs long but every listed field is genuine return-value information the agent needs, since no output schema exists.

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 read-only one-parameter list tool without an output schema, the description covers what is returned, in what order, how many, what is filtered out, and who sees what. Nothing an agent needs in order to call it correctly or interpret the result is missing.

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 wgCode parameter is fully documented in the schema (100% coverage, including the 'leave it out for single-flat accounts' case), so the schema carries the burden. The description never mentions wgCode or how it changes results per flat, adding no meaning beyond structured data, which is the baseline 3.

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 ('List the latest imports'), scopes it precisely (up to 10, newest first, only those import_undo can still reverse), and enumerates the returned fields (id, source, startedAt, inserted, importedByMemberId). It is unmistakably distinct from import_preview and from list siblings.

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 names the use case ('find the importId of an import_commit from an earlier session') and routes the agent elsewhere for the adjacent need ('For the preview of new data use import_preview'). It also states an exclusion rule (imports with settled shares are left out), so the agent knows why expected rows may be absent.

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