Skip to main content
Glama

Get AgentSolis config

get_config
Read-only

Reads the public AgentSolis configuration and cross-checks paused status, public access, fee bps, and fee cap via eth_call, returning both results and a drift list when values differ.

Instructions

Read the public AgentSolis config and cross-check paused, public access, fee bps and fee cap with eth_call. Returns both results and a drift list when they differ. Does not sign, send, or change a deal.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, but the description adds genuinely non-redundant behavior: it performs an eth_call to cross-check, it returns both the read and the cross-check result, and it emits a drift list on mismatch. That tells the agent the call touches a live chain and how to interpret divergence, which no annotation conveys. It does not cover latency, RPC failure modes, or which chain/RPC, leaving a small gap.

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 short sentences, front-loaded with the action and its mechanism, then the return shape, then the safety boundary. Every clause carries information an agent can act on, and there is no preamble or repetition of the title.

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?

With no parameters and no output schema, the description carries the burden of describing returns, and it does so at a high level ('both results and a drift list when they differ'). The phrase 'both results' is slightly underspecified — the config read versus the eth_call verification — leaving the exact response shape to inference. Given the tool's low complexity this is nearly sufficient.

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?

The tool takes zero parameters, so the baseline is 4 and the description correctly adds no parameter guidance. Nothing is misrepresented about inputs.

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 opens with a specific verb and resource ('Read the public AgentSolis config') and names the exact fields being cross-checked (paused, public access, fee bps, fee cap), which makes it distinguishable from deal-oriented siblings like prepare_deal or get_deal_status. It stops short of explicitly naming those siblings as alternatives, so an agent must infer the routing rather than read it.

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 boundary line 'Does not sign, send, or change a deal' effectively excludes side-effecting use, which is useful when-tool-not guidance. However, there is no positive statement of when to reach for this tool (e.g., before preparing a deal, or to verify on-chain config freshness) and no named alternative for acquiring config a different way.

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