Skip to main content
Glama

AINDEX

Arcus pTokens: shorts and leverage on chain

list_ptokens
Read-only

Every Arcus pToken on Robinhood Chain: a share of an Arcus perps account with a fixed market, side and leverage (pHOOD3x a 3x long on HOOD, sBTC a short on BTC). Value per share (posted by Arcus), size, and Uniswap v4 pool depth.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish a safe read (readOnlyHint=true) over live external data (openWorldHint=true), so the description's marginal job is to disclose anything beyond that. It does add that value-per-share is 'posted by Arcus' (a publisher-attributed figure, which hints at trust and freshness characteristics) and that Uniswap v4 pool depth is included. Otherwise it does not say whether results are paginated, ordered, exhaustive, or how stale the quoted values are.

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?

It is a single front-loaded sentence that leads with scope, defines the instrument via two parenthetical examples, then lists the returned fields. The examples are genuinely load-bearing for interpreting names like pHOOD3x and sBTC, though the opening structure built around a colon and dashes is dense for one sentence.

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?

With no input parameters and no output schema, the description carries the burden of saying what comes back, and it does list the three value fields (value per share, size, pool depth). For a simple read-only listing tool this is close to sufficient; pagination or result-count behavior is the main omission.

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 no parameter semantics to compensate for and the baseline of 4 applies. The description correctly does not invent filtering options that the schema does not support.

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 uses a specific verb and resource ('Every Arcus pToken on Robinhood Chain') and defines what a pToken is with two concrete examples (pHOOD3x as a 3x long on HOOD, sBTC as a short on BTC). It also enumerates the data carried per token. It stops short of contrasting itself with nearby siblings like list_assets, discover_tokens, or search_tokens, so an agent must infer the split.

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?

Scope is stated implicitly through 'Every Arcus pToken on Robinhood Chain' and the no-argument schema, so an agent can infer this is an unfiltered enumeration of one protocol's tokens. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to a search or discovery alternative for filtered lookups.

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