Get the full SYX methodology — how the index is constructed, which onchain components are included, how weights are calculated, the measurement windows, and the exclusion rules. Use this when the user asks "how is SYX calculated" or "what does SYX measure" or "what protocols does SYX include".
| 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, so the safety profile is covered. The description adds context about the return content (methodology details, components, weights, windows, exclusions), which goes beyond annotations and helps set expectations.
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 two sentences with no fluff. The first sentence states what the tool does, and the second gives concrete usage examples, maximizing clarity in a compact form.
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?
Given the tool has no parameters and no output schema, the description covers the essential information: what the methodology includes and when to invoke the tool. It is complete for the tool's low complexity.
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, so the baseline is 4. The description doesn't need to explain parameters, and the schema coverage is 100% (vacuously). No additional parameter semantics are needed.
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 uses a specific verb 'Get' and resource 'SYX methodology', and elaborates on exactly what is covered: index construction, onchain components, weights, measurement windows, and exclusion rules. This clearly differentiates from sibling tools like get_syx_components and get_syx_value.
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 explicitly states when to use the tool with example user queries ('how is SYX calculated', 'what does SYX measure'). However, it does not mention when not to use it or explicitly name alternative tools, so it falls short of a 5.
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.
Each tool targets a distinct aspect: listing, details, comparison, search, calculation, recommendation, and SYX components/history/methodology. While search and search_vaults overlap somewhat, their intended usage differs (natural language vs structured filters). No tools are ambiguous in purpose.
All tool names follow a consistent snake_case verb_noun pattern (e.g., calculate_yield, get_syx_value, list_vaults). The one exception, 'search', is still a clear imperative verb, and 'search_vaults' follows the pattern. No mixing of styles or vague verbs.
With 14 tools, the surface is well-scoped for a DeFi yield platform covering vaults, portfolios, SYX index, and platform info. Each tool serves a clear purpose without redundancy or bloat, fitting comfortably within the typical 3-15 range.
The tool set provides comprehensive coverage of the informational domain: listing, details, search, comparison, yield projection, recommendation, and full SYX index data (current, historical, components, methodology). There are no obvious dead ends, and the absence of transaction-oriented features aligns with the server's apparent read-only, knowledge-query purpose.
