Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Set traffic split by role

grona_set_ab_split
Destructive

Set an A/B campaign's Control and Test traffic percentages by immutable campaign ID, validating integer splits total 100 and mapping them to current variation IDs.

Instructions

Read A/B campaign; map Control/Test to current variation ids, validate integer percentages total 100, update by immutable campaign id.

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": {
      "campaignId": "<campaignId>",
      "Control": "<Control>",
      "Test": "<Test>"
    },
    "name": "grona_set_ab_split"
  }
}

Input Schema

NameRequiredDescriptionDefault
TestYes
ControlYes
campaignIdYesOpaque Grona campaign id or externalId.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower. The description nonetheless adds real context the annotations cannot: this is a read-modify-write that re-maps Control/Test onto the campaign's *current* variation ids and validates the integer totals before writing, which explains why the call is non-idempotent. It does not state what happens to the previous split or how validation failure is surfaced, keeping it out of the top band.

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?

A single dense clause chain covering read, map, validate, and write, with the update-by-immutable-id detail front-loaded at the end as the operational key. It is efficient with no filler, though the telegraphic semicolon style makes it slightly harder to parse than plain prose.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and annotations cover the safety profile. What is missing for a destructive, non-idempotent write on a campaign is prerequisite state — whether the campaign must be in a particular status, whether the split can be changed after launch, and what the tool does when the percentages are invalid.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — only campaignId is documented, while Control and Test are bare integers. The description compensates by establishing that these are percentages mapping to Control/Test variations and that they must sum to exactly 100, which is information the schema does not convey. It does not clarify edge cases such as a 0/100 split or the error shape on a bad total.

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 names a specific resource (A/B campaign traffic split) and the verb sequence (read, map, validate, update), which is far more than the title alone. It stops short of explicitly contrasting with grona_update_campaign, so an agent must infer that this is the specialized path for split changes rather than a generic campaign edit.

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?

Usage is strongly implied: use this when changing the Control/Test split of an existing A/B campaign. There is no explicit when-not guidance (e.g., whether it is allowed on a live vs draft campaign, or whether grona_set_campaign_status should be called first), and no sibling is named as an alternative.

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