base_analytics
Fetches Base 0x wallet balance and nonce stats ($0.002 USDC)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes |
WarpPay402 Gateway
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of transparency. It usefully discloses a per-call cost of $0.002 USDC and implies a read-only fetch, but it does not describe response shape, error behavior, rate limits, or authentication needs.
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 a single sentence, front-loaded with the action verb, and includes the cost note without unnecessary detail. Every part earns its place.
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?
For a one-parameter tool the description is nearly sufficient, but key details are missing: whether balance is in wei or ETH, how nonce is represented, and what constitutes an invalid address. The lack of an output schema further increases the burden on the description.
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 0%, so the 'address' parameter is otherwise undocumented. The phrase 'Base 0x wallet' adds useful meaning by indicating the address should be a Base-chain 0x address, but it does not specify exact format, units, or expected validation behavior.
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 states a specific verb ('Fetches') and a precise resource ('Base 0x wallet balance and nonce stats'). This clearly distinguishes the tool from the sibling scraping, extraction, and data-feed tools.
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 intended use is implied by the domain-specific wording, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. An agent must infer usage from the description 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.
TDQS
C2.7/5.0
Disambiguation3/5
The tools are largely distinct, but web_scraper and browser_scraper overlap on web page scraping, and data_feeds and public_data_feed are hard to distinguish without more detail. A few descriptions do help separate output formats, but an agent could still misfire.
Naming Consistency3/5
All names use snake_case and are descriptive, but the naming pattern is mixed: deploy_contract and render_screenshot are verb-first, while smart_contract_verifier, base_analytics, and data_feeds are noun phrases. This prevents a predictable verb_noun convention.
Tool Count4/5
Twelve tools is a reasonable count and each has a defined paid purpose. However, the set spans scraping, data feeds, DeFi yields, and smart-contract deployment, so it feels slightly broad for a single server.
Completeness3/5
Core operations exist for scraping, extraction, deployment, verification, and data feeds, but the surface is incomplete for lifecycle workflows: contracts can be deployed but not called/managed, and data feeds cannot be listed or refreshed. The gaps are noticeable but not fatal for independent one-off API calls.