Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-percent-change-of

Percent Change Of: Computes the percent change from an old value to a new value 🆓 5 free trial calls per signed wallet

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": "x402-percent-change-of"
  }
}

Input Schema

NameRequiredDescriptionDefault
newNo
oldNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / new / description
      Removed value: -"New to process"
    • removedInput schema / properties / old / description
      Removed value: -"Old to process"
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing behavioral: not whether the result is a percent or a decimal, how negative or zero 'old' values are handled, or what the response shape is. A pure formula restatement leaves an agent guessing about edge cases.

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?

The core purpose is front-loaded in a single efficient sentence. The trailing '🆓 5 free trial calls per signed wallet' is promotional noise that does not help tool selection, but it is brief.

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

Completeness2/5

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

With no annotations, no output schema, and 0% parameter documentation, the description should compensate on all fronts but does not. An agent lacks enough information about inputs, output format, and edge-case behavior to call this correctly with confidence.

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 0% for both parameters. The description at least implies the direction of computation ('old value' to 'new value'), which maps to the old/new properties, but it does not state expected format (numeric string vs number), units, or ordering constraints.

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 ('Computes the percent change from an old value to a new value'), which is more precise than a bare restatement of the name. However, it gives no differentiation from near-identical siblings such as x402-percentage-change, x402-percent-change-array, or x402-rate-of-change, so an agent cannot tell which one to pick.

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 prerequisites, and no named alternatives, despite the tool sitting in a dense cluster of percent/rate-of-change tools. The only usage hint is implicit in naming the two inputs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.