Skip to main content
Glama

Show kritisi configuration

show_config

Inspects the effective Kritisi provider configuration and reports whether API keys are set or unset without printing them.

Instructions

Show the effective kritisi provider configuration. API keys are reported as set or unset, never printed.

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": "show_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does deliver one genuinely useful behavioral fact: API keys are reported as set/unset and never printed, so the agent knows the output is redacted and safe to surface. It does not disclose where the configuration is read from (env vars, config file, defaults), whether missing keys cause an error or just show 'unset', or how precedence is resolved — all relevant for a config-inspection tool.

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 with no filler. The core purpose is front-loaded and the security caveat follows immediately, which is the right ordering for an agent that may be deciding whether output is safe to echo back to a user.

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?

For a zero-parameter read-only tool with no output schema, the description covers what is returned at a conceptual level (the effective provider configuration, with secrets masked). A brief note on what the configuration is resolved from, or what an unconfigured provider looks like, would close the remaining gap.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing options such as a provider filter or verbosity flag that the schema does not support.

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?

States a specific verb and resource: 'Show the effective kritisi provider configuration.' The word 'effective' signals resolved/merged configuration rather than raw file contents, which is a meaningful distinction. It does not differentiate from any sibling, but the listed siblings (merge_imports, natspec_document, security_audit) are unrelated operations, so differentiation is not the burden here.

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 only implied: an agent can infer this is the diagnostic tool to call when it needs to know how the provider is configured. There is no explicit when-to-use framing, no statement of prerequisites, and no mention of what to do instead if the configuration is incomplete or the provider is unconfigured.

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