Profitlee-MCP

Copy a scenario

copy_scenario

Duplicate a Profitlee scenario and recalculate its outputs with current fee tables, enabling side-by-side comparison without changing the source.

Instructions

Duplicate an existing Profitlee scenario into a new one. Profitlee reads the source inputs server-side and recomputes outputs, so the copy reflects the current fee tables. The new name defaults to "Copy of " unless you pass name. Counts against the saved-scenario limit. Requires PROFITLEE_API_TOKEN.

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": {
      "id": "<id>"
    },
    "name": "copy_scenario"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Saved Profitlee scenario id returned by list_scenarios or save_scenario.
`name`	No	Optional name for the copy, up to 120 characters. Defaults to "Copy of <source name>".

Output Schema

Name	Required	Description	Default
`response`	No	Profitlee API response confirming the saved scenario create, update, or delete operation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description adds valuable behavioral context: the copy recomputes outputs from current fee tables, counts against the saved-scenario limit, and requires PROFITLEE_API_TOKEN. This fully discloses the tool's side effects and constraints.

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 four sentences, each earning its place: purpose, behavioral effect, naming rule, limit and auth requirement. No fluff or redundancy; front-loaded with the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 2 parameters and an output schema, the description is complete. It covers purpose, side effects, naming, limits, auth, and the server-side recomputation behavior. The sibling context further clarifies its role among other scenario operations.

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?

The schema already documents both parameters thoroughly with descriptions (id and name, including default behavior). The description adds no new parameter-level information beyond what the schema provides, so the baseline score of 3 is appropriate given 100% schema coverage.

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 clearly states the tool duplicates an existing Profitlee scenario into a new one. The verb 'Duplicate' and resource 'Profitlee scenario' are specific, and it distinguishes from siblings like save_scenario (create) and update_scenario (modify).

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?

The description implies when to use the tool (duplicating an existing scenario) and provides important context (server-side recompute, current fee tables, default naming, saved-scenario limit, token requirement). It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to select it appropriately.

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

Deploy Server