Skip to main content
Glama
Sign In
pathiel

pathiel

by Julian-dev28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_config

Read-only

Read the current trading configuration from ~/.pathiel/.agent-config.json, including mode, HIP-3, allow/block lists, and risk profile, without changing anything. Use before updating settings.

Instructions

Get the trading config from ~/.pathiel/.agent-config.json: mode (LIVE or OFF), HIP-3 on or off, coin and HIP-3 dex allow and block lists, the risk profile when set, and every other top-level key. Changes nothing. Use before update_config to see current values and key names; for what the risk profile allows in dollars use get_risk_limits, and for whether trading is enabled use get_status. A missing file reads as the defaults. Returns the config object.

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. Addedv0.6.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it with 'Changes nothing' while adding behavior the annotations cannot convey: a missing file reads as defaults, and the result is the config object with all top-level keys. That fallback semantics is the kind of trait an agent needs before calling and is not available from structured fields.

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 resource and file path come first, then the field inventory, then the safety note, then the alternatives. The field list is long but every item answers 'what will I get back', and 'every other top-level key' efficiently closes the enumeration without listing more.

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?

With no output schema, the description carries the return-value burden itself and does so by naming the shape ('the config object') and its notable keys, plus the missing-file default. Nothing an agent needs to call this correctly or interpret the result is absent.

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 there is nothing to disambiguate and the baseline of 4 applies. The description instead spends its words on return contents, which is the right trade for a no-arg reader.

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 ('Get the trading config') and enumerates the contents (mode, HIP-3 flag, allow/block lists, risk profile, all other top-level keys) plus the file location. An agent can distinguish it from get_risk_limits and get_status purely from the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use this before update_config to learn current values and key names, use get_risk_limits for dollar limits, and get_status for whether trading is enabled. Both the when and the when-not are named with the sibling that covers each case.

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