List runnable Epsilon integration examples (Python cron DCA, LangChain tools, Vercel AI SDK tools, Telegram bot). Fetch full source with get_example. No API key required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful context beyond those: it is a non-authenticated operation ('No API key required'). It does not describe the return shape, but for a simple listing tool the key safety and access behaviors are covered.
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?
Two short sentences deliver the purpose, scope, sibling routing, and auth requirement with no wasted words. The main action is front-loaded and every clause earns its place.
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 zero-parameter, read-only listing tool with an explicitly named sibling for source retrieval, the description is complete. The agent has enough information to decide when to call it and what to expect at a high level.
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 tool has zero parameters and schema coverage is 100%, so there is no parameter burden for the description to carry. The baseline for zero-parameter tools is 4, and the description appropriately avoids inventing unnecessary parameter details.
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 clearly states a specific action ('List') and a specific resource ('runnable Epsilon integration examples'), and it enumerates the exact kinds of examples included. It also explicitly directs the agent to get_example for the full source, which differentiates this tool from its closest sibling.
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 is explicit that this tool is for listing examples, and it names the alternative tool (get_example) to use when fetching full source. It also notes that no API key is required, giving the agent a clear prerequisite signal.
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.
Most tools are clearly separated by resource (orders, quotes, routes, tokens, docs, examples), but market_stats, get_market_overview, and token_volume overlap on volume/engine-wide stats, and get_quote/get_route are closely related. Descriptions mitigate most misselection.
Most accessors use get_/list_/search_ verbs, but five tools (error_catalog, market_stats, order_preflight, recent_swaps, token_volume) use bare noun phrases instead of a consistent verb-first pattern. All names are snake_case and readable, so the mixed verbs are a moderate inconsistency.
At 15 tools the server is at the top of the ideal range and each area (market data, orders, quotes/routing, docs, examples) is represented. A few overlapping stats/volume tools make it feel slightly heavier than necessary, but the count is not a problem.
The read-only surface is fairly complete: quotes, routes, orderbook, order status/list, market stats, token search, docs, examples, and error catalog. However, there are no tools to create/submit or cancel orders, and no wallet/balance/allowance tools, so agents cannot complete an actual trade from quote to execution. This is a notable gap if the server is meant to support trading, not just research/development.