Perkadoo

Create a perk

create_perk

Create a reward a brand can give members: a coupon code, a link or a message. Milestone rewards set in the dashboard are perks too.

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": {
      "brandId": "<brandId>",
      "name": "<name>",
      "kind": "<kind>",
      "value": "<value>"
    },
    "name": "create_perk"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	coupon (a code), url (a link) or message (text).
`name`	Yes	What the brand calls this perk.
`value`	Yes	The coupon code, link or message.
`brandId`	Yes	Brand ID, the project that offers the perk.
`expiresAt`	No	When the perk stops being shown, as an ISO 8601 time.
`validDays`	No	How many days a member has to use it after it's given, like 30. Null keeps it until the perk's own expiry.
`valueCents`	No	What the perk is worth to a member, in cents.
`uniqueCodes`	No	Coupons only. true when each member needs their own code, like a gift card: members wait for one until codes are added, and never get the value.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already declare that this is a non-read-only, non-destructive, non-idempotent, non-open-world mutation. The description adds useful domain context about perk types and milestone rewards, but it does not describe permission requirements, side effects, or what happens after creation. With annotations carrying the safety profile, this is adequate but not rich.

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 two short sentences and is front-loaded with the core action and resource. Every sentence contributes to understanding what a perk is without unnecessary detail.

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 rich input schema, full parameter description coverage, and annotation safety hints, the description provides enough conceptual framing to call the tool correctly. It does not explain return values or post-creation behavior, but the schema and annotations carry most of the operational burden.

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?

Schema description coverage is 100%, so all eight parameters are already documented in the input schema. The description reinforces the 'kind' distinction among coupon, url, and message, but adds little beyond what the schema already states for fields like uniqueCodes, validDays, and expiresAt.

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

Purpose4/5

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

The description uses a specific verb and resource: 'Create a reward a brand can give members,' and immediately names the three supported perk forms: coupon code, link, or message. It clearly identifies what the tool creates, but it does not explicitly differentiate this tool from siblings such as create_giveaway or list_perks.

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?

The description explains what a perk is, but it does not state when to use create_perk versus alternatives, nor does it provide exclusions or prerequisites. The note that milestone rewards set in the dashboard are perks too is conceptual context rather than invocation guidance.

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

All Perkadoo tools Inspect

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

Need Help?