Skip to main content
Glama

SCRIPTMASTERLABS — MNEMOS Options Radar

MNEMOS Gas Recommendation

mnemos_gas_recommend
Read-onlyIdempotent

Paid (x402, 0.001 USD). Returns the gas module's recommendation for a chain: the module name, its stated reason, and whether it abstained. Input: chain (chain identifier; the underlying route defaults to 'eth' when omitted). Without a valid payment proof the call returns the route's 402 payment requirements.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain identifier to evaluate, e.g. 'eth'. Optional — the underlying route defaults to 'eth' when omitted.
payment_signatureNoCaller-supplied x402 v2 PAYMENT-SIGNATURE. Omit to receive the payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / chain / description
      Added value: +"Chain identifier to evaluate, e.g. 'eth'. Optional — the underlying route defaults to 'eth' when omitted."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the paid x402 model with a concrete price (0.001 USD), the 402 fallback behavior, and the 'eth' default for the underlying route. These are exactly the operational facts an agent needs before invoking a paid, open-world read.

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?

Three tight sentences, front-loaded with the paid nature and the return shape, then the input and the failure mode. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description enumerates the return fields and explains the payment-requirements response path, so an agent knows both the success and failure outcomes. Nothing material is missing for a two-parameter read tool.

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 coverage is 100% and the schema already documents both parameters including the 'eth' default, so the description's restatement of the chain default adds no new meaning. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb and resource ('Returns the gas module's recommendation for a chain') and enumerates the returned fields (module name, reason, abstention flag). This is clearly distinct from the sibling scan/scorecard/status tools without needing to name them.

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?

Explains the payment precondition clearly: without a valid payment proof the call returns 402 requirements, and omitting payment_signature yields the requirements. It does not explicitly say when to prefer this over siblings, but the domain is narrow enough that the usage context is clear.

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