Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_get_taxes_report

Read-onlyIdempotent

Retrieves WooCommerce taxes reports. Mirrors woocommerce-mcp-server method get_taxes_report using local WordPress authentication; no WooCommerce REST API keys are required.

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_id": "<site_id>"
    },
    "name": "wc_get_taxes_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number. Default 1.
periodNoReport period. Default month.
dateMaxNoOptional maximum date.
dateMinNoOptional minimum date.
filtersNoWooCommerce REST API report filters to pass through.
perPageNoNumber of results per page. Default 10, max 100.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is handed to the agent. The description adds real context beyond that: it uses local WordPress authentication and requires no WooCommerce REST API keys, which affects setup reasoning. It says nothing about pagination limits, date-range defaults, or what a report contains, leaving those to the schema.

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?

Two short sentences, front-loaded with the purpose; nothing is redundant. The second sentence is implementation/auth metadata rather than usage guidance, which is mildly off-target but still short and informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A seven-parameter reporting tool with a nested open-ended filters object and no output schema deserves at least a hint of what the report returns (tax rates vs. totals, grouping) and valid period values. The definition is complete on authentication and identification but thin on output shape, which the absence of an output schema makes more costly.

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 every parameter (page, perPage, period, dateMin/dateMax, filters, site_id) is already documented in the schema, including defaults and the list_sites prerequisite. The description adds no param-level meaning such as accepted period values or the shape of the pass-through filters object, so baseline 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?

States a specific verb and resource: 'Retrieves WooCommerce taxes reports', which an agent can distinguish from the many sibling report tools (sales, coupons, customers, stock) by the 'taxes' resource. It does not explicitly contrast with the closest alternatives, but the resource noun is specific enough to select correctly.

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?

No when-to-use or when-not-to-use guidance is given; nothing tells the agent how this differs in purpose from wc_get_sales_report or wc_get_orders_report. The only implied prerequisite ('call list_sites first') comes from the schema's site_id description, not the tool description itself.

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources