Skip to main content
Glama

woo_helper_get_invoices

Retrieve a site's invoice configuration and status, including provider API key presence, cached sevDesk/Lexware lists, active invoicing state, and order counts by invoice status.

Instructions

Invoice settings of cvrt-woo-helper 0.4.0+ (sevDesk / Lexware Office): settings, API keys per provider as { set, constant } (never the key), the cached provider lists (contact persons, templates, layouts, ...), whether invoicing is active, and order counts per invoice 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": {
      "site": "<site>"
    },
    "name": "woo_helper_get_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does add genuinely useful disclosure that API keys are returned only as {set, constant} and never as the key itself, and that provider lists are cached — both are non-obvious traits. It stops short of stating read-only semantics, auth/prerequisite requirements, or what happens when invoicing is inactive or the site id is invalid.

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

Conciseness3/5

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

It is a single sentence with no filler, so nothing is wasted, but it is structured as a comma-separated inventory of returned data rather than a front-loaded statement of purpose. The parenthetical '(never the key)' interrupts the enumeration and would read better as a separate clause.

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?

There is no output schema, so the description must describe returns — and it does so thoroughly, covering settings, key presence flags, cached lists, active status, and per-status order counts. For a one-parameter read tool this is close to complete; the only missing piece is routing guidance against the many sibling invoice/settings tools.

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% and the single 'site' parameter is documented in the schema as 'Site id (see list_sites)', so the baseline of 3 applies. The description adds no further meaning about the site parameter, such as whether it selects a multisite blog or a specific integration configuration.

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 names a specific resource (invoice settings for cvrt-woo-helper) and enumerates exactly what it exposes: settings, per-provider API keys as {set, constant}, cached provider lists, invoicing-active flag, and order counts by invoice status. It is distinguishable from woo_helper_get_settings/woo_helper_status by its invoice-specific scope, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus woo_helper_get_settings, woo_helper_status, woo_helper_invoices_test_connection, or woo_helper_invoices_refresh. The 'get' name implies a read, but nothing tells the agent whether this should be called before configuring invoices, after refreshing the cache, or how it relates to the sibling invoice tools.

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