Skip to main content
Glama

greenlit_questions

Read-only

Ask the app owner seven launch questions on backups, spending limits, test databases, webhooks, alerts and email, then return why each gap matters and a fix prompt.

Instructions

Seven launch questions only the app's owner can answer (backups and restore, separate test database, hard spending limits, payment webhook checks, outage alerts, email sender, database plan). Call with no arguments to get the questions and options to ask the user. Call with answers ({questionId: optionKey}) to get, for each gap, the fact that makes it matter and a fix prompt. Answers are the owner's word, never graded.

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

Input Schema

NameRequiredDescriptionDefault
answersNoFor example {"backup": "no", "spend": "alerts"}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description is consistent with that and adds real context beyond it, notably that the call is non-mutating across both modes and that 'answers are the owner's word, never graded' — telling the agent no validation or scoring happens. It also discloses the differing return shape per mode. It does not cover what happens with malformed questionIds or partial answer sets.

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 sentences, front-loaded with the identity of the tool before the mode instructions. The parenthetical topic list is long but earns its place by making the tool's scope concrete. Slightly dense with semicolon chaining, but no filler.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so for both modes (questions and options; then the fact that makes each gap matter plus a fix prompt). Combined with 100% schema coverage on the one param, this is nearly complete — only edge-case behavior for partial or invalid answers 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% and the single optional param is documented as a free-form object, so the schema alone gives only a shape example. The description adds the semantic contract: keys are questionIds, values are optionKeys, and supplying them changes the response into gap explanation plus fix prompt. It does not state what happens for unknown keys or non-answered questions.

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 states a specific resource ('seven launch questions only the app's owner can answer') and enumerates the exact topics covered (backups/restore, test DB, spending limits, webhook checks, outage alerts, email sender, DB plan). That enumeration makes it unmistakably distinct from greenlit_advisor/check/scan without needing to name them. Two invocation modes are also stated outright.

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

Usage Guidelines4/5

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

Usage is explicit for the tool's own two modes: no arguments to retrieve questions and options, `answers` to get per-gap rationale and fix prompts. It does not say when to prefer this over the sibling tools or what prerequisite state (e.g. after a scan) makes it appropriate, so it stops short of full when/when-not guidance.

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