Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_jupiter_dcas

nansen_jupiter_dcas
Read-onlyIdempotent

Jupiter DCA (recurring buy/sell) orders on Solana involving a token: who is DCA-ing in or out, deposit size, amount spent, status. Signals slow, persistent accumulation or distribution. 1 credit.

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": {
      "token_address": "<token_address>"
    },
    "name": "nansen_jupiter_dcas"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1)
limitNoRows to return (1-100, default 20)
labelsNoOnly include wallets carrying at least one of these labels
statusNo
token_addressYesSolana token mint address
min_deposit_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the safety bar is low. The description still adds real value beyond them by disclosing the credit cost (1 credit) and the shape of what comes back (deposit size, amount spent, status), plus the interpretive signal the data provides.

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?

Two dense sentences with no filler: the resource and returned fields come first, the analytical interpretation second, and the cost last. Every clause carries information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and six parameters, the description does part of the work by sketching the returned fields and cost. However, it leaves undefined how the filter parameters (labels, status, min_deposit_usd) affect results and what a row actually represents beyond the headline fields, so it is adequate but not complete.

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 67%, so most parameters are self-documented in the schema. The description only clarifies that the query is token-scoped and returns DCA participants; it says nothing about how labels, status, min_deposit_usd, or pagination shape results, so it neither compensates for the gap nor adds meaning beyond the schema.

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?

States a specific resource (Jupiter DCA recurring buy/sell orders on Solana for a given token) and enumerates the returned dimensions: who is DCA-ing in or out, deposit size, amount spent, status. That distinguishes it implicitly from spot-trade siblings like nansen_token_dex_trades, though it never names an alternative or uses an explicit verb.

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?

Usage is only implied: 'Signals slow, persistent accumulation or distribution' suggests the analytical question it answers, but there is no explicit when-to-use, when-not-to-use, or routing to sibling tools such as nansen_token_dex_trades or nansen_smart_money_trades. An agent must infer selection from the resource name alone.

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