Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Verify Embed installation

grona_verify_script
Read-onlyIdempotent

Verifies that the Grona Embed snippet is present on a specified workspace page URL. Confirms page accessibility and snippet installation, but does not check execution, anti-flicker, consent, or CSP.

Instructions

Check exact page for this workspace’s Embed snippet. absent also means inaccessible page. Does not verify execution, anti-flicker, consent, CSP or whole site. Can take several seconds.

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": {
      "url": "<url>"
    },
    "name": "grona_verify_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) page URL.

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?

Beyond the annotations (readOnly, idempotent, openWorld), the description discloses two genuinely useful traits: an 'absent' result conflates a missing snippet with an inaccessible page, and the call 'can take several seconds'. It also enumerates non-coverage areas (execution, anti-flicker, consent, CSP, whole site), which prevents over-trusting the result. It omits auth/permission requirements, keeping it from a 5.

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, followed by result semantics and limits. The fragmentary phrasing ('absent also means inaccessible page') is terse but readable; no filler is present.

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 single-parameter read-only check with an output schema, the description supplies the key interpretive context: what presence/absence means, what is out of scope, and expected latency. Return-value shape is rightly left to the output schema, leaving only permission requirements unaddressed.

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 100% and the url parameter is already described as an 'Absolute http(s) page URL'. The description's 'exact page' wording reinforces that a concrete page rather than a pattern is expected, but adds little beyond what the schema already conveys, so the baseline of 3 applies.

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 verb and resource: check a specific page for this workspace's Embed snippet. The added caveat that 'absent also means inaccessible page' sharpens what the result actually tells you. It does not name a sibling tool such as grona_generate_snippet for contrast, so it stops short of full differentiation.

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 scope is implied through the phrase 'exact page' plus the exclusion of 'whole site', which signals a single-page presence check rather than a site-wide audit. However, no alternative tool is named and no prerequisites are stated, so the agent must infer when this is the right call versus other verification or readiness tools.

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