Skip to main content
Glama
Sign In
mcp-server-woocommerce

mcp-server-woocommerce

by AmitGurbani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_currencies

Read-only

Retrieve all currencies supported by WooCommerce, including their codes and symbols.

Instructions

List all currencies supported by WooCommerce with their codes and symbols.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated fields to return (default: code,name,symbol)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the agent knows it's a safe read operation. The description adds minor context (returns all currencies, includes codes/symbols) but does not disclose additional behavioral details like pagination, limits, or exact return format. It does not contradict the annotations.

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?

The description is a single, well-structured sentence that front-loads the action and resource. Every word adds value, with no wasted language or redundancy.

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 low-complexity list tool with one optional parameter and read-only annotation, the description adequately explains what it does and the default returned fields. While it doesn't specify the exact JSON return structure, the absence of an output schema and the simplicity of the tool make this sufficient.

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%: the single 'fields' parameter is fully described with its type, default value, and meaning. The description adds no additional parameter semantics, so the baseline of 3 applies.

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?

The description uses the specific verb 'List' and clearly identifies the resource as 'all currencies supported by WooCommerce' with details about what is returned (codes and symbols). This distinguishes it from sibling tools like list_countries or list_products, making the purpose unambiguous.

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?

The description provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or alternative tools. Usage is only implied by the name and purpose, with no direct comparative context.

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