Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Check launch readiness

grona_check_campaign_readiness
Read-onlyIdempotent

Verify a campaign's live or preview page to report observable blockers and required manual checks before launch. Confirm readiness; saved edits and previews cannot be inspected.

Instructions

Read campaign and freshly verify its actual page from stored url or preview URL. Report observable blockers and manual checks. Cannot inspect saved edits or previews.

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>"
    },
    "name": "grona_check_campaign_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description still adds real context: it performs a fresh live fetch of the page rather than reading cached metadata, it returns both observable blockers and items requiring manual checks, and it explicitly cannot see saved edits or previews. That last constraint is a meaningful scope limitation an agent would otherwise not know.

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?

Three short sentences, front-loaded with the core action and followed by output nature and limitation. No filler or repetition. The telegraphic phrasing ('Read campaign and freshly verify its actual page') costs a little readability but not enough to drop below 4.

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?

An output schema exists, so return values need not be described. Combined with annotations covering the safety profile and a fully documented single parameter, the description supplies the remaining essentials: what is fetched, that the check is fresh, what kind of findings come back, and the preview/edit blind spot. Nothing an agent needs in order to call it correctly is missing.

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?

There is a single required parameter with 100% schema coverage, and the schema already explains that it accepts an opaque campaign id or externalId. The description adds nothing further about id format, resolution behavior, or what happens with an invalid id. Baseline 3 is appropriate when the schema fully carries parameter documentation.

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?

States a specific action and resource: read a campaign, then freshly verify its actual page from a stored or preview URL, and report blockers and manual checks. That is materially distinct from siblings like grona_get_campaign or grona_campaign_overview, though the description never names those siblings to sharpen the contrast. The phrasing 'Read campaign and freshly verify' is slightly compressed but the intent is clear.

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 line 'Cannot inspect saved edits or previews' functions as an implicit when-not hint, steering agents toward edit-link validation for unpublished changes. However, no alternative tool is named and there is no positive trigger such as 'use before calling launch_campaign.' Usage is inferable but not explicit.

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