Skip to main content
Glama
Sign In

Perkadoo

by com.perkadoo
OverviewDiscussionsAdmin

Build my giveaway and streak from my site

build_prebuild_from_site

Give Doo your site's address. Doo reads it and builds your giveaway, daily streak and perks in your brand colors, then returns a private preview link. Nothing goes live until you make it yours from that page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "build_prebuild_from_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYour site's address, like yoursite.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare non-read-only, open-world, non-idempotent, and non-destructive behavior. The description adds useful context that the tool reads an external site, returns a private preview link, and does not publish anything live until the user confirms on the preview page.

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 three short, front-loaded sentences with no wasted text. It moves logically from input to generated output to the safety guarantee that nothing goes live automatically.

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?

For a one-parameter creation tool with annotations covering side-effect behavior, the description is nearly complete: it names the generated assets, preview outcome, and publishing guardrail. Minor gaps remain around site prerequisites or what happens on repeated builds, but the essential operational picture is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter and schema description coverage is 100%, so the schema already explains that url is the site address. The description supports this but does not add format, validation, or example details beyond the schema.

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 states a specific action (builds), specific outputs (giveaway, daily streak, perks), and a specific source (the user's site). It clearly distinguishes this auto-generation workflow from sibling tools like create_giveaway, create_perk, and create_streak_badge.

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?

It gives clear usage context: provide a site address so Doo can read it and generate branded assets. It does not explicitly name alternatives or say when not to use this tool compared with create_giveaway or create_perk, but the workflow context is clear enough to route correctly.

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

All Perkadoo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources