Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Validate or refresh editor link

grona_validate_edit_link

Validates a Grona editor link and returns the original or refreshed URL. Always open the returned editUrl; valid=false with refreshed=true indicates success.

Instructions

Send the whole editor URL; receive original or refreshed link. Always open returned data.editUrl. valid=false/refreshed=true is successful.

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": {
      "editUrl": "<editUrl>"
    },
    "name": "grona_validate_edit_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
editUrlYesWhole Grona editor link exactly as issued.

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 declare readOnlyHint=false and openWorldHint=true, but the description adds genuinely non-obvious behavior: the call may return the original or a refreshed link, callers must use the returned data.editUrl rather than the one they sent, and success is signaled by valid=false/refreshed=true. The success condition is counterintuitive and valuable, though the wording is terse enough that an agent could misread it, and it never says whether a refresh invalidates the prior link.

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, front-loaded sentences with no filler: input, return, and success criterion in order. The final sentence is compressed to the point of being slightly cryptic, but nothing is redundant.

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 not be enumerated, and the description still flags the field to act on (data.editUrl) plus how to read the success flags. Given openWorldHint and a non-read-only annotation, it could say more about whether a refresh issues a new link and invalidates the old one, which is the main remaining gap.

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 single parameter already documents "Whole Grona editor link exactly as issued." The description echoes that constraint ("Send the whole editor URL") but adds no new syntax, format, or validation detail beyond the schema, 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?

"Send the whole editor URL; receive original or refreshed link" states a concrete input and output for validating/refreshing a link, matching the title. It is clear what the tool does, though it never explicitly contrasts itself with the sibling grona_create_edit_link, so the boundary between creating and validating a link must be inferred.

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?

It gives an input-side rule (send the whole URL) and a post-call rule (always open data.editUrl), which is actionable usage guidance. However, it never states when to prefer this over grona_create_edit_link or what to do when a refresh is not desired, so the when-to-use decision is only implied.

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