Skip to main content
Glama
eidostein

@segnals/mcp

by eidostein

segnals_copy_strategy

Copy a marketplace strategy to your bots using a two-step process: preview the listing and cost, then confirm to execute. Buyer risk disclaimer required before confirming.

Instructions

Copy a strategy from the marketplace to your bots. Requires scope: write:marketplace.

TWO-STEP CONFIRMATION: Call without confirm to preview the listing and cost. Call with confirm: true to copy. FREE strategies: copied immediately. PAID strategies: initiates a crypto payment flow. The buyer risk disclaimer is required — the agent must present the disclaimer to the user before confirming.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listing_idYesMarketplace listing ID to copy
confirmNoSet to true to execute after previewing
Behavior5/5

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

With no annotations, the description fully discloses the two-step flow, scope requirement (write:marketplace), behavior for free vs paid strategies, and the mandatory disclaimer, ensuring the agent understands the tool's full behavior.

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 concise with no wasted words, front-loading the purpose, and using clear bullet-like structure for the workflow steps.

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?

Covers all necessary aspects for a two-parameter tool: workflow, free/paid distinction, disclaimer requirement, and scope. Minor omission of error or response details, but sufficient for correct invocation.

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?

While schema coverage is 100%, the description adds significant context for the 'confirm' parameter by explaining the preview-then-execute flow, which goes beyond the schema's definition.

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 verb 'copy' and the resource 'strategy from the marketplace', and distinguishes it from siblings like 'segnals_browse_marketplace' and 'segnals_get_listing' by focusing on the copy action.

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?

Explicitly describes the two-step confirmation process (preview without confirm, execute with confirm), differentiates free vs paid strategies, and mandates the buyer risk disclaimer, providing clear when-to-use and prerequisites.

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/eidostein/segnals-mcp'

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