Skip to main content
Glama

set_revenue_plan

DestructiveIdempotent

Capability seller commits immutable collaborator trial-credit shares before the first quote. Sum at most 10000 basis points; seller gets remainder and rounding. Confirm rights and intended recipients before committing. No cash moves.

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": {
      "capability_id": "<capability_id>",
      "splits": "<splits>"
    },
    "name": "set_revenue_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
splitsYes
capability_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true; the description earns credit by explaining why — the commit is immutable, so there is no undo path — and by adding the rounding/remainder rule and the 'No cash moves' scope limit, which prevents the agent from mistaking this for a payment operation. It stops short of saying what error surfaces if the total exceeds 10000 bp.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, with the action and the immutability caveat front-loaded and the scope disclaimer ('No cash moves') last. Dense but no filler; the only cost is the compressed jargon in the opening clause.

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 two-parameter destructive write with no output schema, the description covers irreversibility, the numeric constraint, rounding behavior, and a pre-commit verification step — enough for an agent to call it safely. Minor gaps are failure modes and post-commit visibility of the plan.

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 0%, so the description must carry the load. It does explain basis_points well (sum capped at 10000, seller absorbs remainder and rounding), but says nothing about capability_id or recipient_id eligibility — notably whether recipients must be actual collaborators.

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 states a concrete action ('commits immutable collaborator ... shares') on a concrete resource ('capability'), and the basis-point/remainder language makes clear this is a revenue/credit split plan. The phrasing is jargon-heavy ('trial-credit shares') and never names the read-side sibling get_revenue_plan, so differentiation relies on the tool name rather than the text.

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?

It gives real timing guidance ('before the first quote') plus a pre-commit check ('Confirm rights and intended recipients'), which tells the agent where in the workflow this belongs. It does not say when not to use it, whether it can be called repeatedly, or point to get_revenue_plan for inspecting existing plans.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources