Skip to main content
Glama

import_strategy

Idempotent

Parse and validate a shared strategy JSON, performing redaction checks to block address or transaction hash smuggling. Returns a validated object for read-only inspection with no on-chain effects.

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 claims read-only and no side effects, but annotations set readOnlyHint=false and destructiveHint=false (non-destructive but potentially mutating). This contradiction undermines transparency. Per rules, score is 1 due to contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured with a clear front-load of purpose. Each sentence adds distinct information (validation, redaction, shape rules, read-only nature). Slightly long but well-organized.

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?

Given no output schema, the description explains return value and metadata. It covers validation rules, redaction, and side-effect status. However, it omits details on error handling beyond RedactionError and might benefit from specifying valid JSON requirement.

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 100% schema coverage, the description adds value beyond the schema by clarifying the two accepted forms (string from jsonString vs object from strategy) and linking them to share_strategy outputs. This enhances usability.

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 parses and validates a shared-strategy JSON from share_strategy, distinguishing it from the producing tool. It specifies the action (parse and validate) and the resource (shared-strategy JSON), making the purpose unambiguous.

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 indicates when to use (after receiving a JSON from share_strategy or user), provides input format options (string or object), and explains the redaction scan for security. It lacks explicit when-not-to-use or alternatives but is generally clear.

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/vaultpilot-mcp'

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