Skip to main content
Glama

import_strategy

Idempotent

Parse and validate a shared-strategy JSON. Return the validated strategy for read-only inspection; reject JSON containing addresses or tx hashes.

Instructions

Parse and validate a shared-strategy JSON produced by share_strategy (someone else's, or one the user generated earlier). Pass either the stringified form or the parsed object via json. Returns the validated SharedStrategy for read-only inspection — protocol allocations, per-position percentages, optional health-factor / fee-tier / APR metadata. The same redaction scan that runs on emit also runs on import — addresses or tx hashes anywhere in the imported JSON cause a RedactionError, so a malicious sender cannot smuggle a wallet identifier through fields the recipient might not eyeball. Strict shape validation: unknown fields tolerated (forward-compat for v2 schema additions) but required fields must be present and well-typed. Read-only — no on-chain side effect, no signing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonYesThe strategy JSON. Pass either the stringified form (what `share_strategy` returns in `jsonString`) or the parsed object (what it returns in `strategy`). The same redaction scan that runs on emit also runs on import — addresses or tx hashes anywhere in the imported JSON cause a structured RedactionError.
Behavior1/5

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

The description states 'Read-only — no on-chain side effect, no signing', but annotations have readOnlyHint=false, which contradicts this. Per guidelines, a contradiction scores 1. Additional behavioral info like redaction scan and validation rules is useful but undermined by the contradiction.

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 description is detailed but well-structured, with the main purpose upfront followed by specifics on usage, validation behavior, and safety. Every sentence adds information, and it avoids unnecessary repetition. It is appropriately sized for the tool's complexity.

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?

Despite lacking an output schema, the description fully explains the return value ('validated SharedStrategy for read-only inspection') and covers key aspects: input types, redaction scanning, strict shape validation with forward-compatibility, and the read-only nature. This provides sufficient context for an AI agent.

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?

With schema coverage at 100%, the baseline is 3. The description adds value by explaining how to pass the JSON (stringified or parsed object) and referencing the output of share_strategy. This goes beyond the schema's description, justifying a 4.

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?

The description clearly states the tool's purpose: 'Parse and validate a shared-strategy JSON produced by share_strategy'. It specifies the resource (shared-strategy JSON), the action (parse and validate), and distinguishes it from the sibling tool 'share_strategy' which presumably exports the JSON.

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?

The description explains when to use this tool: when you have a shared-strategy JSON to validate and inspect. It clarifies that it works for both someone else's strategy or one the user generated earlier, and mentions return for read-only inspection. However, it does not explicitly state when not to use it or mention alternatives beyond share_strategy.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/szhygulin/recon-crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server