WPBay

Get a WPBay product

get_wordpress_product

Read-onlyIdempotent

Retrieve authoritative public WPBay catalog details for a known canonical product ID, including compatibility, pricing options, public license, seller, maintenance information, documentation, and previews when available.

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": {
      "product_id": "<product_id>"
    },
    "name": "get_wordpress_product"
  }
}

Input Schema

Name	Required	Description	Default
`product_id`	Yes

Output Schema

Name	Required	Description	Default
`product`	Yes
`api_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by enumerating the returned data fields and noting the 'authoritative public' nature, which is useful context beyond the annotations. No contradictions found.

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?

A single, efficient sentence that front-loads the action and then enumerates the returned details. No filler or redundant phrasing, earning every word.

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 simple one-parameter read-only tool with an output schema, the description is complete. It explains what is retrieved, mentions optional availability of previews, and does not omit critical information for correct invocation.

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 coverage is 0%, so the description must compensate. It identifies the parameter as a 'product ID' and adds 'canonical', implying a standardized identifier, but provides no further detail on format, source, or how to obtain it. The schema already defines type and constraints, so the description adds marginal meaning.

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 clearly states the tool retrieves WPBay catalog details for a known product ID, listing the specific data categories (compatibility, pricing, license, seller, maintenance, documentation, previews). This differentiates it from the sibling search tool, which would be used to find products, and compare, which compares multiple products.

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

Usage Guidelines4/5

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

The phrase 'known canonical product ID' implies the tool is intended when you already have a specific product ID, contrasting with search_wordpress_software for discovery. However, it does not explicitly name the alternative or state when not to use it, leaving some inference required.

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

All WPBay tools Inspect

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

Need Help?