Perkadoo

Set the brand's goal

set_goal

Idempotent

Aim a brand at more new faces or more returning members: a number to reach by a deadline. Doo plans around it and Home tracks it. Replaces the current goal, which is kept as history.

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>",
      "metric": "<metric>",
      "target": "<target>",
      "deadline": "<deadline>"
    },
    "name": "set_goal"
  }
}

Input Schema

Name	Required	Description
`metric`	Yes	new_faces counts first-time members who left an email. returning counts members active in two or more weeks.
`target`	Yes	The number to reach.
`brandId`	Yes	Brand ID, the project Doo runs.
`deadline`	Yes	When to reach it, within the next 366 days. ISO 8601 with an offset.

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 already declare this is a non-read-only, non-destructive, idempotent operation. The description adds meaningful behavioral context beyond the annotations: setting a goal replaces the current one, and the old goal is preserved as history, which helps the agent understand the overwrite semantics.

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 sentences, front-loaded with the core action and followed by useful system behavior and replacement semantics. Every sentence contributes without repetition or filler.

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?

With four required parameters, full schema coverage, and annotations covering safety and idempotency, the description supplies the key missing context: this replaces the current goal while preserving history. It does not explain return values, but no output schema exists and the core call semantics are sufficiently clear.

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 the schema already documents all four parameters thoroughly, including the metric enum and deadline constraints. The description reinforces the high-level meaning of metric, target, and deadline but does not add syntax or constraints beyond what the schema provides, so baseline 3 is appropriate.

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 clearly conveys that this sets a brand goal with a target number and deadline, and it clarifies the two metric modes (new faces vs. returning members). It is specific enough to distinguish setting a goal from reading one via get_goal, though it relies on the title to supply the literal verb 'set'.

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?

The description implies usage by explaining what a goal is for and that it replaces the current goal, but it does not explicitly say when to use this tool versus get_goal or other sibling tools. The replacement behavior is useful but not framed as usage 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?