Skip to main content
Glama
Grona MCP

Grona MCP

by gbasilveira

Inspect configuration

grona_configuration
Read-onlyIdempotent

Displays credential-presence flags, hosts, and timeout/retry settings without exposing secrets or making upstream requests, so you can verify configuration before use.

Instructions

Show credential-presence flags, hosts and timeout/retry settings without secrets. Makes no upstream request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "grona_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing redaction ('without secrets') and that the call performs no upstream request — meaning the flags reflect presence only, not live credential validity. That is a non-obvious behavioral caveat an agent would otherwise misread as a successful connectivity check.

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?

Two short sentences, zero filler, with the returned payload described first and the no-side-effect guarantee second. Nothing is redundant with the title and nothing needs trimming.

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 no parameters, a full output schema, and rich annotations, the definition carries only the burden of naming return contents and side effects — both done. The one small gap is that it does not say how an agent should interpret a false credential flag (i.e., that configuring credentials requires a different tool).

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. No misleading parameter hints are present.

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 names a specific verb ('Show') and enumerates the exact contents returned: credential-presence flags, hosts, and timeout/retry settings. It is unambiguous what an agent gets back, and no sibling in the catalog shares this configuration-inspection purpose, so differentiation is implicit rather than stated.

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 is implied rather than stated: an agent can infer this is the diagnostic call to check whether credentials and hosts are configured. There is no explicit 'use this when...' phrasing, no exclusion of alternatives, and no note about what to do if flags come back false.

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