Skip to main content
Glama

pm_smart_money_entries

Read-onlyIdempotent

Smart-money entry feed: wallet, side, $, price, time, lag, and whether GT logged it live, late, or rebuilt it afterwards. Newest 3 free; the rest paid.

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

Input Schema

NameRequiredDescriptionDefault
nNo1 to 500, paid callers only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond that by disclosing data provenance categories (live, late, rebuilt) and a free/paid access boundary, though it does not detail auth handling or rate limits.

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?

The description is two tight sentences, front-loads the feed's purpose, and lists returned fields compactly. There is no redundant or filler text.

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 simple one-parameter read feed with no output schema, the description sufficiently explains the returned data fields and the live/late/rebuilt logging distinction. It leaves minor gaps around default behavior and how n affects the free/paid split, but is otherwise 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 100%, and the single parameter n is already documented as ranging from 1 to 500 for paid callers. The description's paid-access note is consistent but does not add syntax or 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?

The description identifies a specific resource, a smart-money entry feed, and enumerates the returned fields such as wallet, side, price, time, lag, and logging status. It is clear what the tool provides, though it does not explicitly distinguish itself from siblings like pm_wallet_record or pm_market_board.

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 pricing note 'Newest 3 free; the rest paid' gives useful access context but does not say when to choose this feed over sibling tools or when not to use it. Usage is implied by the resource name rather than explicitly guided.

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.