Perkadoo

Start a streak badge

create_streak_badge

Start a personal streak for any habit with Perkadoo's Streak Badge, no account needed. Returns a public streak page, a live SVG badge for a README or website, and a private check-in link. The check-in link is the only way to check in, so tell the person to save it.

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": {
      "title": "<title>"
    },
    "name": "create_streak_badge"
  }
}

Input Schema

Name	Required	Description
`theme`	No	Badge colours. Default light.
`title`	Yes	The habit, e.g. 'Read 20 pages' or 'Ship a commit'.
`timeZone`	No	IANA time zone that decides when a day starts, e.g. Europe/London. Default UTC.
`ownerName`	No	Whose streak it is, shown on the public page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare a non-read-only, open-world, non-idempotent creation, and the description adds real value beyond that: it enumerates the three artifacts produced (public page, live SVG, private check-in link) and warns that the check-in link is unrecoverable-by-design ('the only way to check in, so tell the person to save it'). It stops short of saying a repeat call creates a duplicate badge, which matters given idempotentHint=false.

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?

Three short sentences, front-loaded with the action and followed by returns and the one critical caveat. No filler and nothing repeated from the schema.

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 create tool with no output schema, the description covers what is produced and the key risk of losing the private link. It leaves open how the caller later retrieves or manages the badge (get_streak_badge, check_in_streak_badge), which a slightly longer description could have routed.

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 coverage is 100%, with each parameter documented including the theme enum and timeZone example, so the schema already does the work. The description contributes only the framing of 'any habit', which maps loosely to title and adds no format or default detail beyond the schema.

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 opens with a specific verb and resource ('Start a personal streak ... with Streak Badge') and names the product, so the action is unambiguous. It does not explicitly contrast itself with the sibling get_streak_badge or check_in_streak_badge, relying on 'Start' vs 'get' to carry the distinction.

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

Usage Guidelines3/5

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

'no account needed' gives a prerequisite in the negative, and the note about saving the check-in link is an operational instruction. But there is no explicit statement of when to choose this tool over get_streak_badge or what to do if a streak already exists, so usage is only implied.

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?