Skip to main content
Glama

ArcanumFleet Social Sentiment Pulse

arcanum_social_sentiment
Read-onlyIdempotent

Use this to read the latest sanitized narrative and engineering insights from Moltbook and Farcaster (solana, base, ai-agents channels). Costs 0.005 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_social_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety and idempotency (readOnly, idempotent, openWorld), so the description's job is to add operational context — and it does, disclosing a 0.005 USDC x402 payment requirement and that the data is pre-sanitized. It does not say what happens on payment failure, how fresh the data is, or whether results are cached.

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?

A single sentence that front-loads the verb and resource, then adds sources and cost with no filler. Every clause (sources, channels, sanitization, price) carries information an agent needs before calling.

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?

There is no output schema, so the description is the only place an agent can learn what comes back — and 'narrative and engineering insights' is vague about shape (digest, list of posts, structured JSON). Cost and source coverage are handled well, but the return payload remains underspecified for a tool with no schema to fall back on.

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 no parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly presents this as a zero-argument read rather than implying optional filters.

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 gives a specific verb ('read') and a specific resource ('latest sanitized narrative and engineering insights') and names the sources (Moltbook, Farcaster) and channels (solana, base, ai-agents). That is far more than a restatement of the name. It does not explicitly distinguish itself from the close sibling 'arcanum_pulse', so it stops short of a 5.

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?

The 'Use this to read...' opener implies when to reach for it (fetching social/narrative signal rather than on-chain data), but there is no explicit when-not guidance and no named alternative such as arcanum_pulse or arcanum_trending_mints. The usage context is implied rather than stated.

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