Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Generate Embed snippet

grona_generate_snippet
Read-onlyIdempotent

Generate escaped Embed HTML with optional page-variable assignment for Grona snippets, including anti-flicker for dashboard usage; this helper does not install anything.

Instructions

Generate escaped Embed HTML and optional page-variable assignment. Dashboard snippet may include anti-flicker; this helper installs nothing.

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": {
      "workspaceId": "<workspaceId>"
    },
    "name": "grona_generate_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
segmentIdNoCustom window variable name, up to 128 characters.
workspaceIdYes
segmentValueNoExact page-variable string match.

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 readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real value by saying the output is escaped HTML, that a page-variable assignment may be included, that dashboard snippets may carry anti-flicker code, and that nothing is installed as a side effect.

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?

Two short sentences, front-loaded with what is produced, followed by the key behavioral caveat. No filler or restatement of the name.

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 shape need not be explained, and annotations cover safety. However, for a generation tool the description leaves open what determines anti-flicker inclusion and what workspaceId controls, gaps an agent would want closed before invoking it.

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 67% and the two segment parameters already carry descriptions, so the schema does most of the work. The phrase 'optional page-variable assignment' links segmentId/segmentValue to the output, but the description says nothing about workspaceId's role or when to supply the optional parameters, so it adds only marginal meaning.

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 verb and artifact: 'Generate escaped Embed HTML and optional page-variable assignment.' The scope (escaped HTML, optional page-variable) is clear enough to distinguish it from write-oriented siblings like grona_create_edit_link, though no sibling is named explicitly.

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 clause 'this helper installs nothing' implicitly frames it as a non-mutating helper, and the anti-flicker remark hints at the dashboard context, but there is no explicit when-to-use/when-not guidance or routing to alternatives such as grona_create_edit_link or grona_verify_script.

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