Skip to main content
Glama

ArcanumFleet Market Pulse

arcanum_pulse
Read-onlyIdempotent

Use this first for a broad snapshot of live sanitized Solana momentum and audit signals across the fleet. Does not require a mint address. Costs 0.002 USDC via x402.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds genuinely useful non-schema context: the 0.002 USDC x402 payment cost, that data is 'live' and 'sanitized', and that no mint address is needed. It does not indicate response shape, freshness window, or what 'sanitized' means.

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?

Three short sentences, front-loaded with the entry-point instruction and ending with the cost. Every sentence carries unique information - usage priority, scope, parameter shape, and price - with no filler.

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 zero-parameter, read-only snapshot with annotations covering safety and no output schema, the description supplies the essential operating context including the paid-call requirement that an agent must know before invoking. A brief hint at the categories of signals returned would close the last gap.

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 for a parameterless tool applies. The note that no mint address is required usefully confirms the empty schema is deliberate rather than truncated.

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 and scope: a broad snapshot of live Solana momentum and audit signals across the fleet. 'Use this first' and 'does not require a mint address' implicitly separate it from the mint-parameterized siblings, though no sibling is named.

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?

'Use this first' is explicit ordering guidance, and 'does not require a mint address' tells the agent when this applies versus mint-addressed tools. No sibling is named outright, so it stops short of a full when/when-not/alternative statement.

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