ScorpTech x402 Tools

Vampire Low

vampire_low

Read-onlyIdempotent

The smaller fang of a vampire number. 1260 gives 21, 1395 gives 15, and 6880 gives 80. A non-vampire is rejected. n runs from 1 to 9999. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/vampire-low

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": {
      "n": "<n>"
    },
    "name": "vampire_low"
  }
}

Input Schema

Name	Required	Description	Default
`n`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare a safe read-only, idempotent operation, and the description adds meaningful context: paid x402 execution, USDC cost, Solana context, an HTTPS endpoint, and rejection of non-vampire inputs. The only gap is that 'rejected' is not defined as a specific error or response shape.

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?

The description is short, front-loaded with the core definition, and uses examples efficiently. Pricing and endpoint details are compact and relevant rather than padding.

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 one-parameter computational tool with rich annotations and no output schema, the description supplies enough to call it correctly: examples, valid range, rejection behavior, and payment details. It is not fully complete on error semantics or sibling routing, but it is adequate overall.

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?

The single parameter n is constrained to 1 through 9999, but that range is also present in the schema. The examples help by showing n=1260 returning 21 and similar mappings, which clarifies that n is the vampire number to inspect, though the description does not add much beyond the schema and examples.

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 identifies the tool as returning the smaller fang of a vampire number, and the examples make the input-output relationship concrete. It distinguishes itself somewhat from the broader vampire siblings by specifying 'smaller fang,' but it does not explicitly name or route against siblings like vampire_fangs or vampire_next.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the valid input range and that non-vampire numbers are rejected, which gives implied usage context. However, it does not say when to choose this tool over vampire, vampire_fangs, vampire_count, or vampire_next, nor does it explain the rejection behavior in detail.

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

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