Skip to main content
Glama

x402-price-earnings

Price Earnings: Computes the price-to-earnings ratio as price divided by earnings 🆓 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-price-earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceNo
earningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / earnings / description
      Removed value: -"Earnings to process"
    • removedInput schema / properties / price / description
      Removed value: -"Price to process"
  2. Changed2 schema fields changed
    • addedInput schema / properties / earnings
      Added value: +{
      +  "description": "Earnings to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / price
      Added value: +{
      +  "description": "Price to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/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. It does disclose the payment/auth model ('5 free trial calls per signed wallet'), which is useful behavioral context the schema cannot convey, but it says nothing about input validation, rounding, negative earnings handling, or the return shape for a math tool.

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?

A single front-loaded sentence that delivers purpose, formula, and billing note with no padding. The trailing trial-call emoji note is slightly promotional but not wasteful.

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 simple two-input arithmetic tool with no output schema, the description covers what the tool does and how the inputs combine, which is sufficient to call it. Minor gaps remain around input format and result format, but nothing critical is missing.

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 does partly: the formula 'price divided by earnings' tells the agent which argument is numerator vs denominator, adding real meaning beyond the bare property names. But with both params typed as unconstrained strings, nothing explains expected numeric format or units.

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 ('computes') and resource ('price-to-earnings ratio') and even spells out the formula, so the operation is unambiguous. However, it does nothing to distinguish itself from the nearly identical sibling x402-pe-ratio, leaving the agent to guess which of the two to call.

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 mention of the duplicate sibling x402-pe-ratio or of related tools like earnings-yield. The only context given is the free-trial note, which is billing information rather than usage direction.

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.

Resources