EVM gas price — Current gas price for Base or Ethereum mainnet, in gwei and wei. Source: public RPC. JSON. Price: $0.002 USDC (Base, via x402).
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | base | ethereum (default base) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as read-only and non-destructive. The description adds meaningful behavior beyond the annotations: it discloses the data source (public RPC), response format (JSON), and the cost in USDC via x402. This is useful operational context for an agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded, packing the core purpose, supported chains, units, source, response format, and pricing into a short text with no wasted words. Every sentence contributes actionable information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-optional-parameter read-only tool with no output schema, the description is quite complete: it states chains, units, source, response format, and pricing. The only minor gap is that it does not detail the exact JSON return shape beyond mentioning gwei/wei and JSON.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already fully documents the chain parameter with its allowed values and default. The description restates the supported chains but does not add substantial new meaning beyond what the schema provides, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb/resource: it provides the current EVM gas price for Base or Ethereum mainnet. It also specifies units (gwei and wei), making the tool's purpose unambiguous and distinct from sibling tools like crypto_balance or crypto_token_report.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly indicates the tool is for retrieving current gas prices on Base or Ethereum, giving an agent enough context to select it. It does not explicitly name alternative tools or state when not to use it, but the purpose is specific enough that exclusion is largely unnecessary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools are clearly separated by prefix and data source, but several bundled products overlap heavily: vehicle_deal_check vs vehicle_report, realestate_property_report vs realestate_site_risk, finance_company_360 vs finance_health_scan, and domain_due_diligence vs email_domain_check/business_vet. An agent would frequently struggle to pick the correct premium bundle.
Tool names overwhelmingly follow a consistent snake_case category-prefix pattern like weather_, crypto_, vehicle_, finance_, and geo_. Minor deviations such as bare names (domain, ip) and noun-verb forms (dns_lookup, url_check) are easy to learn and don't create real confusion.
50 tools is far beyond the typical well-scoped 3–15 range and will require heavy filtering to navigate. The broad multi-domain data marketplace partially justifies the size, but it would be more coherent split into per-domain servers or consolidated further.
For a read-only data/diligence marketplace, the surface is quite comprehensive: weather, vehicle, crypto, SEC/finance, domain/email, sanctions, and geo workflows all have core operations plus fused verdict bundles. Minor gaps exist—such as a simple crypto price lookup or vehicle market value—but agents can usually work around them.