Shipfound

Giveaway: what to propose

giveaway_plan

What a giveaway starts from: the product (what it does, its buyers and their pains, from the brief), its feature ideas and peer study patterns when there are any, where it can post (X and Reddit, by the audit and the notes cadence), the subreddits that take a founder's post with their rules, any giveaway running (replies, waiting, delivered), the four shapes (a result done for each person, capped credits or usage, an asset, founding seats) with how each is delivered, a cost line per shape at the default cap of 10, and the rules every giveaway keeps. unitCostUsd: what one use of the product costs the founder when it pays AI or API costs per use, asked once and kept. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "giveaway_plan"
  }
}

Input Schema

Name	Required	Description	Default
`unitCostUsd`	No	What one use of the product costs the founder, in dollars, as they said

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations say readOnlyHint=false, so the tool does persist something, and the description usefully explains that unitCostUsd is 'asked once and kept', plus discloses where its inputs come from (the brief, the audit, the notes cadence). It does not say what exactly gets written or what the response looks like, so it adds only partial context beyond the annotations.

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

Conciseness2/5

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

The whole definition is one ~120-word run-on sentence with a dense comma-separated enumeration of eight-plus deliverables. The opening 'What a giveaway starts from' is front-loaded, but the rest is unscannable and several items (peer study patterns, notes cadence) are unexplained jargon.

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?

Since there is no output schema, the description must carry the return content, and it does so thoroughly — listing every component of the plan including the four shapes and per-shape cost line at a cap of 10. What is missing is the precondition/sequence (what must exist before calling) and how the plan is used downstream.

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 already 100%, but the description adds real meaning: the cost applies 'when it pays AI or API costs per use' and is 'asked once and kept', clarifying both the semantic condition and the persistence behavior. That is genuine value beyond the schema's plain 'cost per use in dollars'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the content of the plan (product, feature ideas, posting channels, subreddits, running giveaways, four shapes, cost line, rules) but never states a verb or the output form — it reads as 'this is a bag of things' rather than 'returns a proposed giveaway plan'. An agent can roughly infer intent from the title and the list, yet it is not distinguished from siblings such as giveaway_start or giveaway_mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisite (e.g. an existing brief or audit), and no mention of the obvious alternative giveaway_start. The only implicit signal is 'what a giveaway starts from', which leaves the agent to guess the ordering in the workflow.

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

All Shipfound tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?