SiteCheck Crypto & Finance

Blast L2 native yield from the chain itself

crypto_blast_gold_points

Read-only

Blast L2 native yield from the chain itself: for the rebasing USDB (stablecoin yield) and WETH (ETH staking yield) predeploy contracts, total supply and share price — the cumulative native-yield multiplier since launch (e.g. 1.126 = 12.6% earned) — plus latest/safe/finalized blocks, finality lag, gas price and block time. Blast Gold / DApp points are allocated off-chain by Blast and have no public API, so they are not reported. Blast shut down: it stopped producing blocks on 5 Nov 2026, so the answer is its final on-chain state and says so (chainHalted, haltedSince). Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "crypto_blast_gold_points"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`head`	No
`safe`	No
`chain`	No
`source`	No
`chainId`	No
`checkedAt`	No
`finalized`	No
`headToSafe`	No
`nativeYield`	No
`gasPriceGwei`	No
`avgBlockTimeSec`	No
`headToFinalized`	No
`gasUsedPctOfLimit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the most decision-relevant behavior: the chain is dead and the answer will be a frozen final state, the response carries chainHalted and haltedSince flags, and billing is $0.002 in USDC per successful call via x402 with failed calls free. The halt disclosure in particular prevents an agent from misreading stale data as live.

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?

Extremely dense and front-loaded, with the most important fact (what is measured) first and the halt notice and pricing after. The first sentence is long and comma-chained, which slightly hurts readability, but nearly every clause carries substantive information.

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?

Output schema exists so return values need not be enumerated, yet the description still surfaces the two fields that change interpretation (chainHalted, haltedSince). Given the halted-chain situation and the paid-call model, the description covers everything an agent needs to call and correctly interpret this tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly implies a single fixed query scope with no filtering options.

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?

Names the specific resources (USDB and WETH predeploy contracts on Blast L2) and the exact metrics returned (total supply, share price/native-yield multiplier, latest/safe/finalized blocks, finality lag, gas price, block time). It also explicitly disambiguates against the tool's own name by stating Blast Gold/DApp points are off-chain and not reported, so an agent won't expect them.

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?

Clear about the situation in which results should be read (chain halted since 5 Nov 2026, so output is final on-chain state, flagged via chainHalted/haltedSince) and about the negative case (Gold/DApp points unavailable). It does not name a sibling tool or explicitly route the agent elsewhere for L2 metrics, so it stops short of full when/when-not guidance.

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

All SiteCheck Crypto & Finance 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?