Skip to main content
Glama
kouko

redshift-comment-mcp

by kouko
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_setup_status

Verify whether a Redshift profile is configured without touching the database. Returns status fields and a next-step hint to guide proactive setup decisions.

Instructions

Read-only check of whether a profile is configured. Safe to call at any time including the very start of a session — does not touch Redshift, does not return any secrets.

Use at session start to decide proactively whether to call setup_via_dialog (before triggering any DB tool's not_configured error path), or to verify a setup_via_dialog call succeeded from a fresh angle.

Returns:

  • profile — the queried profile name

  • source — "inline" when the server was launched in legacy inline mode (--host/--user/--dbname + REDSHIFT_ PASSWORD env, e.g. the Claude Code plugin UI), else "profile". In inline mode the profile/keychain path is bypassed entirely, so don't go hunting for an active profile.

  • configured — bool, equivalent to has_fields && has_password

  • has_fields — whether config.toml has this profile's non-secret fields (host / port / user / dbname); in inline mode, True (the fields came from launch args)

  • has_password — whether a password is available (OS keychain in profile mode; REDSHIFT_PASSWORD / --password in inline mode). NEVER returns the password itself

  • host / port / user / dbname — present only when has_fields=True (these are non-secret)

  • next_step — present only when configured=False; actionable hint pointing at the right mechanism for the mode

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNodefault

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

No annotations provided, so the description fully carries the burden. It states 'read-only', 'does not touch Redshift', 'does not return any secrets', and explains return fields including behavior in inline mode. This is comprehensive and transparent.

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 well-structured with clear sections and bullet points for returns. It is information-dense but not overly verbose. A slight reduction in the return list could improve conciseness, but it remains effective.

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?

Given the simple input and presence of an output schema, the description covers all necessary aspects: safety, use cases, return details, inline vs profile mode distinctions, and actionable hints. It is fully complete for this tool.

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?

The input schema has one parameter 'profile' with 0% description coverage. The description does not explicitly describe the input parameter; it only mentions 'the queried profile name' in the return section, which implies but does not clearly state that the input specifies which profile to check. The added value is marginal.

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

Purpose5/5

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

The description clearly states the tool is a 'read-only check of whether a profile is configured' with specific verb and resource. It distinguishes itself from siblings like 'setup_via_dialog' and 'execute_sql' by noting it does not touch Redshift and is safe to call at any time.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly provides when to use: at session start to decide proactively whether to call 'setup_via_dialog', or to verify a setup call succeeded. It also advises against hunting for an active profile in inline mode, offering clear context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kouko/redshift-comment-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server