Skip to main content
Glama

ScorpTech x402 Tools

Unit Sum

unit_sum
Read-onlyIdempotent

The reduced sum of unit fractions 1/d. Dens must be positive. An empty list or a non-positive denominator is rejected. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/unit-sum

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": {
      "dens": "<dens>"
    },
    "name": "unit_sum"
  }
}

Input Schema

NameRequiredDescriptionDefault
densYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds useful behavioral context beyond annotations: $0.001 USDC per successful x402/Solana call, an HTTPS endpoint, and rejection conditions for empty or non-positive inputs.

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?

Front-loads the mathematical definition, then gives essential constraints, then pricing/endpoint information. The sentences are short and every part adds useful information.

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?

The tool is simple and annotations cover safety traits, but there is no output schema and the description does not state the return format, e.g. whether the reduced sum is returned as a numerator/denominator pair or a string. Validation and payment context are covered, but return semantics are missing.

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

Parameters4/5

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

Schema coverage is 0% for the single dens parameter, so the description must compensate. It explains that dens are denominators of unit fractions, must be positive, and that empty or non-positive denominators are rejected; minor mismatch with schema minimum 0 is a small confusion but the description clarifies intended valid input.

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 operation: the reduced sum of unit fractions 1/d, with dens as denominators. It is clear what the tool computes, though it does not distinguish itself from nearby siblings such as egyptian_sum or harmonic.

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?

Provides validation constraints (positive denominators, non-empty list) and pricing/HTTPS access details, but gives no explicit guidance on when to use this tool versus alternatives. The agent must infer usage from the mathematical purpose.

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