Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Get campaign

grona_get_campaign
Read-onlyIdempotent

Retrieve a campaign using its opaque Grona ID or workspace-unique externalId; the Grona ID takes precedence on ambiguity, and editor links are not returned.

Instructions

Get by opaque Grona id or workspace-unique externalId. Grona id wins on ambiguity. No editor links return.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "grona_get_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesOpaque Grona campaign id or externalId.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds two genuine behavioral facts beyond that: identifier precedence and the caveat that no editor links are returned. It does not say what happens when the id is unknown (error vs empty), which matters for a lookup tool.

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 with no filler, and the lookup-key semantics are front-loaded. The phrasing is telegraphic ('No editor links return'), which costs a little readability, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple single-parameter read tool with an output schema, so return values need not be explained, and the description covers both identifier forms and their precedence. Combined with full schema coverage and complete annotations, nothing essential to correct invocation is missing.

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 100%, so the baseline is 3, but the description adds real meaning: campaignId is either an opaque Grona id or a workspace-unique externalId, and the Grona id takes precedence on ambiguity. That precedence rule is not present in the schema and directly affects how the agent populates the single required parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Get by opaque Grona id or workspace-unique externalId', which conveys single-item retrieval keyed by identifier, but the resource noun ('campaign') is only supplied by the name/title, and the verb 'Get' is generic. It does not distinguish itself from grona_list_campaigns or grona_search_campaigns, so the agent must infer that this is the direct-lookup path.

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 only guidance is an intra-parameter disambiguation rule ('Grona id wins on ambiguity'), which is useful but concerns which identifier form to pass, not when to choose this tool over list/search siblings. Usage is implied by the identifier-based framing rather than stated.

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