PAL Commerce & Agent Revenue MCP

Paid product feed diff

feed_diff

Compare two product-feed snapshots and return added, removed, and changed commerce fields that can affect AI-shopping and feed accuracy. Price: $0.01 USDC via x402.

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": {
      "before": "<before>",
      "after": "<after>"
    },
    "name": "feed_diff"
  }
}

Input Schema

Name	Required	Description
`after`	Yes
`before`	Yes
`payment_signature`	No	Optional x402 v2 PAYMENT-SIGNATURE value. Omit it on the first call to receive the live payment requirement; supply the signed value on the second call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

B3.1/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. It usefully discloses the cost model ($0.01 USDC via x402) and that the operation is a comparison returning a diff set, but it never states the 100-item caps, whether the operation is purely read-only, or how the two-step payment handshake behaves (that detail lives only in 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.

Conciseness5/5

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

Two sentences, zero filler, with the core verb/resource front-loaded ahead of the pricing note. Every sentence earns its place.

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?

For a 3-parameter, no-output-schema, no-annotation paid tool, the description covers purpose and cost but leaves the return shape undefined (no output schema to fall back on) and the diff semantics vague. It is adequate to attempt a call but not complete for correct interpretation of results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — before and after are undocumented objects. The description says they are 'snapshots' and the names imply ordering, but it never explains the expected record shape, how products are matched between snapshots, or what happens when a field is absent in one side.

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 states a specific verb and resource (compare two product-feed snapshots) plus the return set (added, removed, changed commerce fields), so an agent immediately knows what it does. It does not explicitly differentiate itself from siblings like catalog_audit or gtin_check, which keeps it short of a 5.

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 when-to-use guidance, no statement of when-not-to-use it, and no pointer to alternatives such as catalog_audit or single_gtin_check. The only routing signal is the price, which tells the agent it is a paid tool but not when it is the right one.

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

All PAL Commerce & Agent Revenue MCP 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.