storyflo

Get crypto market exposure link (Kraken affiliate)

get_crypto_market_link

Read-onlyIdempotent

Return Storyflo's markets-partner Kraken affiliate URL for a given crypto asset (BTC, ETH, etc). Editorial linkout, not a trading prompt: the URL points at Kraken's public asset page so a listener who wants exposure can reach a regulated venue without leaving the brief context. Markets-as-INPUT posture (counsel-cleared) — Storyflo never quotes prices, never recommends positions, and never frames exposure as risk-free.

Behavior

Read-only. No persistent server state.
Idempotent — same (asset, embedder_slug) returns the same URL.
Fail-closed — when KRAKEN_AFFILIATE_ENABLED is off OR the partner base URL is unset, the call returns an error structure rather than a half-formed URL.
Attribution-aware — pass embedder_slug to credit the embedding publisher in the affiliate ?ref parameter; default falls back to ?ref=storyflo so the link is always trackable.

When to use Surface the link in show-notes copy or in MCP-client renderings of a crypto-relevant story. DO NOT inline the URL into spoken audio narration without the host-read line that frames it as an editorial signal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`asset`	Yes	Primary crypto asset symbol — BTC, ETH, SOL, USDC, etc. Case-insensitive; upper-cased before being embedded in the URL.
`embedder_slug`	No	Optional embedder attribution slug. When set, the affiliate URL carries ?ref=<slug>; omit to default to ?ref=storyflo.

TDQS

A4.5/5.0

Behavior4/5

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

The description adds operational context beyond the annotations: read-only, idempotent, fail-closed (error when disabled/unconfigured), and attribution-aware with default slug. Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description complements rather than repeats these, providing valuable extra details.

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 well-organized with sections ('Behavior', 'When to use') and uses clear, direct language. While detailed, it avoids unnecessary verbiage. Could be slightly trimmed, but structure aids readability.

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 the tool's complexity (affiliate URL generation, fail-closed behavior, attribution) and the absence of an output schema, the description covers essential aspects: error handling, default behavior, and usage context. It provides sufficient completeness for an agent to use correctly.

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?

Schema coverage is 100% (both parameters documented). The description adds extra semantics: for 'asset', it notes case-insensitivity and upper-casing before embedding; for 'embedder_slug', it explains the default fallback to '?ref=storyflo' and the attribution purpose. This additional context goes beyond the basic schema descriptions.

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 returns a Kraken affiliate URL for a given crypto asset. It specifies the exact action ('Return') and resource ('Storyflo's markets-partner Kraken affiliate URL'). It distinguishes from siblings by noting it is an editorial linkout, not a trading prompt, and that it is markets-as-INPUT posture.

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?

Explicit 'When to use' section advises to surface the link in show-notes copy or MCP-client renderings of crypto-relevant stories. It explicitly warns against inlining into spoken audio without a host-read framing line. This clearly delineates appropriate usage from misuse.

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

All storyflo tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation4/5

Most tools have distinct purposes, but there is overlap between `get_my_private_feed`, `subscribe_topic`, and `list_subscriptions`—all return or manage feed URLs, which could confuse an agent. Otherwise, categories like publisher, fund manager, and search tools are clearly separated.

Naming Consistency5/5

All tools use consistent snake_case with a verb_noun pattern (e.g., `get_article`, `search_articles`, `publisher_upload_audio`). Exceptions like `digest` are single-word verbs but still fit the pattern. No mixed conventions are present.

Tool Count2/5

With 37 tools, the server exceeds the 25-tool threshold considered 'too many' by the rubric. While the broad scope (news, podcasting, publishing, fund management, embedding) justifies a large surface, the count still adds cognitive load and would benefit from splitting into separate servers.

Completeness4/5

The tool set covers the major domains: search, retrieval, subscriptions, publishing, fund manager operations, and embedder network. Minor gaps exist, such as the absence of an unsubscribe or delete-episode tool, but the core workflows are well-supported and agents can accomplish most tasks.

Resources

Need Help?