ScorpTech x402 API

Depreciation

depreciation

Read-onlyIdempotent

Depreciation schedules: straight-line, declining balance (any factor, optional switch to straight-line), double-declining, sum-of-the-years-digits and US MACRS GDS (3/5/7/10/15/20-year, half-year convention, computed from the IRS rules: 200% or 150% DB switching to straight-line). Year-by-year depreciation, accumulated depreciation and book value. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/depreciation

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": {
      "cost": "<cost>",
      "lifeYears": "<lifeYears>"
    },
    "name": "depreciation"
  }
}

Input Schema

Name	Required	Description	Default
`cost`	Yes	Asset cost (basis)
`method`	No		straight-line
`salvage`	No	Salvage value (ignored by MACRS)
`dbFactor`	No	declining-balance factor (2 = double)
`lifeYears`	Yes	Useful life; for MACRS the recovery class 3, 5, 7, 10, 15 or 20
`switchToStraightLine`	No	Declining balance: switch to straight-line when it gives more

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond that: the $0.002 USDC x402 payment requirement, the HTTPS endpoint, the exact output fields (year-by-year, accumulated, book value), and MACRS-specific IRS rules including half-year convention and 200%/150% DB switching.

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 description is a single dense paragraph that front-loads the methods and outputs, then adds payment and endpoint details. Every sentence carries information, though the pricing and URL could be visually separated for faster scanning.

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?

With no output schema, the description correctly explains return values (year-by-year depreciation, accumulated depreciation, book value) and covers all computational modes, payment mechanics, and the alternate HTTPS route. Nothing essential for correct invocation is 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 83%, so the baseline is 3, but the description adds real meaning: dbFactor is any factor, switchToStraightLine is optional, and lifeYears for MACRS is a recovery class limited to 3/5/7/10/15/20. That supplements the schema's enum and parameter descriptions rather than repeating them.

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 names the exact resource (depreciation schedules) and enumerates every supported method, from straight-line through MACRS GDS. No sibling tool computes depreciation, so the scope is unambiguous without needing to name an alternative.

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 method list gives clear context for when each calculation style applies, and parameter notes (dbFactor, switchToStraightLine, MACRS recovery classes) help the agent choose correctly. There is no explicit when-not-to-use guidance, but no competing sibling exists.

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

All ScorpTech x402 API 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?