Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Fetch mobile grants

grona_issue_grants
Read-onlyIdempotent

Fetches current signed mobile grants for an authenticated shopper using a customer ID, returning tokens unchanged without verifying or redeeming them.

Instructions

Fetch current signed grants from separate mobile service/credential. customerId must come from authenticated shopper session, never app input or PII. Return tokens unchanged; this does not verify or redeem them.

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": {
      "customerId": "<customerId>"
    },
    "name": "grona_issue_grants"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYesOpaque shopper id from an authenticated session, never an email, phone or national id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new behavior: tokens are returned unchanged and the call neither verifies nor redeems them, which tells the agent there are no downstream state changes to the grants themselves. It stops short of describing error cases or what an empty result means.

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?

Three short sentences, zero filler, with the purpose first and the security constraint and non-verification caveat following. Every sentence carries information an agent needs.

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?

With one parameter, full schema coverage, an output schema, and rich annotations, the description covers purpose, the trust boundary for the identifier, and what the call does not do. Only minor gaps remain, such as the behavior when no grants exist or when the mobile service is unavailable.

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 customerId parameter is already fully documented in the schema, including the prohibition on email/phone/national id. The description restates the same authenticated-session constraint rather than adding new meaning, so the baseline 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?

"Fetch current signed grants from separate mobile service/credential" gives a specific verb (fetch) and resource (signed grants) plus the source system. An agent can tell this apart from the campaign-management siblings, though the phrase "separate mobile service/credential" is somewhat vague about what that backend actually is.

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 through the sourcing constraint on customerId and through the boundary "this does not verify or redeem them," which hints at a different tool for those actions. However, it never states when an agent should call this versus a verification/redeem path, and names no alternative explicitly.

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