Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Simulate page targeting

grona_evaluate_page_targeting
Read-onlyIdempotent

Evaluate page-targeting URL rules and optional page-variable matches before launch. Predict eligibility to catch excluded pages early, without affecting traffic allocation.

Instructions

Locally evaluate URL rules and optional page-variable value. Multiple-page exclusions still require exact origin and segment count. Predicts eligibility, not execution or traffic allocation.

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

Input Schema

NameRequiredDescriptionDefault
urlYesOriginal campaign sample URL retained from creation.
listNo
slugNo
typeNogeneral
urlsYes
conditionNoincluded
segmentIdNoCustom window variable name, up to 128 characters.
segmentValueNoExact page-variable string match.
pageTargetingNospecific
pageVariablesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, closed-world operation. The description adds meaningful behavioral context by stating that evaluation is local, that it predicts eligibility only, and that it does not cover execution or traffic allocation, plus the exact-origin/segment-count caveat.

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?

The description is short and front-loaded, with no filler. The middle sentence about multiple-page exclusions is important but somewhat terse and could be clearer.

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?

The output schema and annotations reduce the need to explain return values and safety, and the description captures the main simulation boundary. However, for a 10-parameter evaluation tool, it leaves too many input relationships and modes unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 10 parameters and only 30% schema description coverage, the description needs to compensate substantially. It mentions URL rules and an optional page-variable value, and hints at multiple-page exclusion constraints, but it does not explain key parameters such as list, slug, type, condition, pageTargeting modes, or how url and urls differ.

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 uses a specific verb, "evaluate," and names the resource, URL rules/page targeting, so the tool's function is clear. It does not explicitly distinguish itself from sibling campaign-management tools, which keeps it below 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by saying it locally evaluates URL rules and clarifies that it predicts eligibility rather than execution or traffic allocation. It gives an important caveat about multiple-page exclusions, but it does not explicitly say when to use this tool versus related validation or launch tools.

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