Skip to main content
Glama

Blazar Polygon plugin

Wallet portfolio: native, tokens, LP, staking, USD

blazar_portfolio
Read-onlyIdempotent

One call for a wallet's balances with USD on Polygon (default), Base or Ethereum (chain param). Polygon: native POL, every BlazarForce-list token (plus up to 20 extra tokens you pass), BlazarSwap LP positions with underlying amounts, BZB staking v1 (staked, earned) and staking v2 position, USD from the Blazar oracle. Base / Ethereum (chain param): native ETH plus the curated token list and your extra tokens, USD from DefiLlama. null = unknown, never guessed. Read-only.

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": {
      "account": "<account>"
    },
    "name": "blazar_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain: "polygon" (default, chain 137), "base" (8453) or "ethereum" (1). BZB / BlazarSwap tools are Polygon only.
tokensNoExtra tokens beyond the chain's curated list (addresses or verified symbols).
accountYesWallet to read.

Output Schema

NameRequiredDescriptionDefault
noteNo
chainNo
nativeNo
tokensNo
accountNo
chainIdNo
stakingNo
asOfBlockNo
lpPositionsNo
knownValueUsdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the safety profile is free. The description still earns credit by disclosing behavior beyond them: the per-chain pricing source (Blazar oracle on Polygon vs DefiLlama on Base/Ethereum), differing asset coverage between chains, and the data-quality contract 'null = unknown, never guessed', which tells the agent not to infer missing values.

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?

Front-loaded with the core purpose and default chain, then split cleanly into Polygon-specific and Base/Ethereum-specific coverage so the agent can read only the branch that applies. It is a single dense block with list-heavy clauses that could be broken into sub-bullets for faster scanning, but no sentence is filler.

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 an output schema present, the description need not explain return shapes, and with full annotation coverage it need not explain safety. What remains - per-chain asset coverage, USD source differences, the 20-extra-token limit, and null semantics - is all addressed, so an agent can call this correctly on any of the three chains without further lookup.

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 description coverage is 100%, so all three parameters are already documented and the baseline is 3. The description does add consequence-level meaning not in the schema - that the chain choice changes both the asset universe and the USD source - but it does not explain the token-resolution or address-over-symbol nuances beyond a passing mention of the 20-extra-token cap.

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 first clause gives a specific verb and resource ('One call for a wallet's balances with USD') plus the chain scope, and the following sentences enumerate exactly what categories are returned (native, curated tokens, extra tokens, LP positions with underlying amounts, staking v1/v2, oracle USD). This clearly separates it from siblings like blazar_staking_info, blazar_tokens, or blazar_prices, which return single facets.

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?

'One call' plus the category enumeration implies this is the consolidated read tool an agent should prefer over composing several sibling calls, and the chain parameter default is stated so the agent knows the common path. It stops short of explicit exclusions (e.g. 'for a single token price use blazar_prices'), so the guidance is strong context but not a full when/when-not rule.

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