Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Create editor link

grona_create_edit_link

Creates a secret 15-minute editor link for a variation using variationId (preferred) or page URL so the editor can be opened immediately.

Instructions

Mint a secret 15-minute editor link by variationId (preferred) or page url. variationId wins; url chooses most recently updated match. Editor trust covers the workspace. Open immediately; do not store, log or share.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "grona_create_edit_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoAbsolute http(s) page URL.
variationIdNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false), the description discloses the 15-minute expiry, that the link is a secret, that trust spans the entire workspace, and an explicit open-immediately / do-not-store-log-share handling rule. Nothing contradicts the annotations, and the non-idempotent hint is implicitly consistent with minting a fresh link each call, though the description never says repeated calls yield distinct links.

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?

Four short clauses, front-loaded with the action and the expiry, then the parameter precedence, then the trust scope and handling rule. No filler and nothing buried.

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?

An output schema exists, so return values need no explanation, and the description covers expiry, scope, precedence, and handling. The one gap is that both parameters are optional (required: 0) yet the description never says what happens if neither is supplied, which is a real ambiguity for an agent that may call it blind.

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 coverage is only 50% (variationId carries no description), and the description compensates meaningfully by declaring variationId the preferred key, establishing precedence when both are supplied, and explaining the selection rule for url. That is real semantic value the schema does not provide.

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?

"Mint a secret 15-minute editor link" gives a specific verb and a precisely characterized resource, with the two accepted lookup keys named. It is clearly distinguishable from the validation sibling, though it never names that sibling explicitly, which keeps it just short of a 5.

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 tells the agent which parameter to prefer (variationId) and what happens when the fallback (url) is used, including tie-breaking by most-recently-updated match. It does not state when to reach for this tool versus grona_validate_edit_link or any other sibling, so the 'when-not' half is absent.

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