Read a public Floatout product, pricing, security or operator guide as Markdown. Returns current published content with its source URL. Does not sign in or change a platform.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / path / enumPrevious value: -[
- "/",
- "/affiliate",
- "/architecture",
- "/authors/staxstallion",
- "/community-pilot",
- "/community-trading-platform",
- "/demo",
- "/guides",
- "/hyperliquid-builder-codes",
- "/hyperliquid-builder-fee-calculator",
- "/hyperliquid-builder-revenue",
- "/hyperliquid-prediction-markets",
- "/hyperliquid-white-label-comparison",
- "/launch-a-perp-dex",
- "/launch-playbook",
- "/partners",
- "/prediction-market-fees",
- "/prediction-market-partner-program",
- "/prediction-market-platform-comparison",
- "/prediction-markets",
- "/prediction-platform-vs-market-creation",
- "/pricing",
- "/sports-macro-community-growth",
- "/terms",
- "/trader-funds",
- "/white-label-crypto-exchange"
-]New value: +[
+ "/",
+ "/about",
+ "/affiliate",
+ "/architecture",
+ "/authors/staxstallion",
+ "/community-pilot",
+ "/community-trading-platform",
+ "/demo",
+ "/guides",
+ "/hyperliquid-builder-codes",
+ "/hyperliquid-builder-fee-calculator",
+ "/hyperliquid-builder-revenue",
+ "/hyperliquid-prediction-markets",
+ "/hyperliquid-white-label-comparison",
+ "/launch-a-perp-dex",
+ "/launch-playbook",
+ "/partners",
+ "/prediction-market-fees",
+ "/prediction-market-partner-program",
+ "/prediction-market-platform-comparison",
+ "/prediction-markets",
+ "/prediction-platform-vs-market-creation",
+ "/pricing",
+ "/sports-macro-community-growth",
+ "/terms",
+ "/trader-funds",
+ "/white-label-crypto-exchange"
+]Input schema / properties / path / enumPrevious value: -[
- "/",
- "/abyss",
- "/affiliate",
- "/architecture",
- "/authors/staxstallion",
- "/community-pilot",
- "/community-trading-platform",
- "/demo",
- "/guides",
- "/hyperliquid-builder-codes",
- "/hyperliquid-builder-fee-calculator",
- "/hyperliquid-builder-revenue",
- "/hyperliquid-prediction-markets",
- "/hyperliquid-white-label-comparison",
- "/launch-a-perp-dex",
- "/launch-playbook",
- "/partners",
- "/prediction-market-fees",
- "/prediction-market-partner-program",
- "/prediction-market-platform-comparison",
- "/prediction-markets",
- "/prediction-platform-vs-market-creation",
- "/pricing",
- "/sports-macro-community-growth",
- "/terms",
- "/trader-funds",
- "/white-label-crypto-exchange"
-]New value: +[
+ "/",
+ "/affiliate",
+ "/architecture",
+ "/authors/staxstallion",
+ "/community-pilot",
+ "/community-trading-platform",
+ "/demo",
+ "/guides",
+ "/hyperliquid-builder-codes",
+ "/hyperliquid-builder-fee-calculator",
+ "/hyperliquid-builder-revenue",
+ "/hyperliquid-prediction-markets",
+ "/hyperliquid-white-label-comparison",
+ "/launch-a-perp-dex",
+ "/launch-playbook",
+ "/partners",
+ "/prediction-market-fees",
+ "/prediction-market-partner-program",
+ "/prediction-market-platform-comparison",
+ "/prediction-markets",
+ "/prediction-platform-vs-market-creation",
+ "/pricing",
+ "/sports-macro-community-growth",
+ "/terms",
+ "/trader-funds",
+ "/white-label-crypto-exchange"
+]Input schema / properties / path / enumPrevious value: -[
- "/",
- "/abyss",
- "/affiliate",
- "/architecture",
- "/authors/staxstallion",
- "/bitget-hack",
- "/community-pilot",
- "/community-trading-platform",
- "/crypto-affiliate-programs",
- "/demo",
- "/discord-server-monetization",
- "/guides",
- "/hyperliquid-builder-codes",
- "/hyperliquid-builder-fee-calculator",
- "/hyperliquid-builder-revenue",
- "/hyperliquid-prediction-markets",
- "/hyperliquid-white-label-comparison",
- "/its-so-over-were-so-back",
- "/kalshi-volume-controversy",
- "/launch-a-perp-dex",
- "/launch-playbook",
- "/partners",
- "/prediction-market-fees",
- "/prediction-market-partner-program",
- "/prediction-market-platform-comparison",
- "/prediction-markets",
- "/prediction-platform-vs-market-creation",
- "/pricing",
- "/sports-macro-community-growth",
- "/telegram-channel-monetization",
- "/terms",
- "/trader-funds",
- "/white-label-crypto-exchange"
-]New value: +[
+ "/",
+ "/abyss",
+ "/affiliate",
+ "/architecture",
+ "/authors/staxstallion",
+ "/community-pilot",
+ "/community-trading-platform",
+ "/demo",
+ "/guides",
+ "/hyperliquid-builder-codes",
+ "/hyperliquid-builder-fee-calculator",
+ "/hyperliquid-builder-revenue",
+ "/hyperliquid-prediction-markets",
+ "/hyperliquid-white-label-comparison",
+ "/launch-a-perp-dex",
+ "/launch-playbook",
+ "/partners",
+ "/prediction-market-fees",
+ "/prediction-market-partner-program",
+ "/prediction-market-platform-comparison",
+ "/prediction-markets",
+ "/prediction-platform-vs-market-creation",
+ "/pricing",
+ "/sports-macro-community-growth",
+ "/terms",
+ "/trader-funds",
+ "/white-label-crypto-exchange"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false; the description usefully reinforces this with 'does not sign in or change a platform' and adds return details ('current published content with its source URL'). It stops short of noting freshness/caching or error behavior for invalid paths, but the safety profile is well covered.
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?
Three short sentences, front-loaded with purpose, then return value, then the safety constraint. No filler, though the 'does not sign in or change a platform' clause overlaps with annotations.
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?
For a one-param read tool with annotations and no output schema, the description covers what is fetched, the format (Markdown), that the source URL is returned, and the non-mutating nature. Nothing an agent critically needs is missing.
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?
Schema coverage is 0%, so the description must carry weight, and it does partially by characterizing the pages as 'public product, pricing, security or operator guide' content. The single `path` parameter is a 27-value enum that is largely self-documenting, but the description adds no detail about path format (leading slash, root '/') beyond what the enum shows.
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?
States a specific verb (read) and resource (public Floatout product/pricing/security/operator pages) plus the output format (Markdown). It's clear what the tool does, though it doesn't explicitly differentiate from siblings like list_floatout_plans or read_builder_fee_study.
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?
Implies usage via 'public' content and the negative constraint 'Does not sign in or change a platform,' which tells the agent this is a read-only public fetch. However, it never states when to pick this over list_floatout_plans or read_builder_fee_study, leaving the routing to inference.
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.