Skip to main content
Glama

woo_helper_invoices_refresh

Reload invoicing provider lists—contact persons, templates, payment methods, and units—into the settings cache. Read-only at the provider, it fixes stale cached data before creating invoices.

Instructions

Reload the provider's lists (contact persons, templates, letter papers, payment methods, units, print layouts, payment conditions) into the settings cache. Read-only at the provider.

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_invoices_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
providerNoDefault: the configured provider

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value by clarifying scope of effect: it writes to the local settings cache but is read-only against the provider. It does not say whether existing locally customized settings are overwritten or preserved, whether the refresh is idempotent, or what the response contains. Useful but incomplete behavioral disclosure for a mutation-of-local-state tool.

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 short sentences, front-loaded with the action and its target, then the side-effect boundary. The parenthetical list is dense but purposeful, and nothing is wasted.

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?

For a two-parameter cache-refresh tool with no output schema, the definition covers what is refreshed and where the read/write boundary lies. The remaining gap is whether a refresh clobbers existing local settings and what it returns, which matters for an agent deciding to call it.

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%, so the schema already documents 'site' (with a pointer to list_sites) and 'provider' (with a default). The description adds no meaning beyond that — it never mentions site scoping or the provider switch, so the baseline of 3 applies.

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 action (reload into the settings cache) and enumerates exactly what is loaded: contact persons, templates, letter papers, payment methods, units, print layouts, payment conditions. That is far more specific than a bare name restatement and distinguishes it from woo_helper_get_settings and woo_helper_update_settings by scope. It stops short of naming an alternative tool, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool to call when the cached provider lists are stale or after configuration changes, but the description never states the trigger condition, prerequisites, or when to prefer woo_helper_get_settings instead. No explicit exclusions or alternatives are given.

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