Skip to main content
Glama
Sign In
The Stall

The Stall

by thebrierfox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

base-season

Provides Base chain TVL snapshot, top 10 native protocols, category breakdown, 7-day trend, and top ecosystem tokens market cap for pre-trade orientation.

Instructions

Base chain season snapshot: total chain TVL, top 10 protocols by Base-native TVL, category breakdown, 7d trend, and top Base ecosystem tokens by market cap. No input required — agents use this for pre-trade orientation before DeFi, lending, or liquidity calls on Base.

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": "base-season"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It lists the data returned (TVL, protocols, etc.), implying a read-only operation. However, it does not explicitly state that the operation is safe or discuss data freshness or 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?

Two concise sentences: first lists contents, second gives usage context. No wasted words, front-loaded with essential information.

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 tool with no output schema, the description provides sufficient context: what data is returned and when to use it. It could improve by mentioning output format or an example, but overall complete.

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?

No parameters exist, so the description correctly has no param info. Baseline for 0 params is 4, and the description does not need to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool provides a snapshot of Base chain TVL, top protocols, category breakdown, trend, and ecosystem tokens. It distinguishes itself from siblings like 'chain-pulse' or 'defi-market-pulse' by specifying the Base chain and the specific data items.

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?

The description advises using this tool for pre-trade orientation before DeFi actions on Base. It implies when not to use (for other chains or execution), but does not explicitly list alternatives or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools