Skip to main content
Glama

greenlit_scan

Read-only

Scans a project folder for launch-blocking misconfigurations like missing RLS, unverified webhooks and exposed secrets before deploying, and returns a fix prompt for each finding.

Instructions

Read a project folder on this computer for launch mistakes that can't be seen from outside, before deploying: Row Level Security policies whose condition is just true, tables created without RLS, Supabase edge functions with verify_jwt = false, Stripe webhook handlers that never verify the signature, secrets behind a public prefix (VITE_, NEXT_PUBLIC_), a tracked .env file, and an agent config with a writable database connection. Pattern-based, not a full code review. Reads names in .env files, never values. Each finding has a fix prompt.

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_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoThe project folder. Defaults to the current folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description still adds real value beyond that: it discloses a privacy behavior (reads names in .env files, never values), a fidelity limit (pattern-based, not a full code review), and that each finding carries a fix prompt. It doesn't say how findings are ordered, how many are returned, or how long a scan takes.

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?

Front-loaded with the verb and purpose, and the scope disclaimer plus privacy note are well placed. The long enumeration of detected patterns is dense and comma-heavy within a single sentence, but each item earns its place by telling the agent what it will and won't report.

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?

No output schema exists, so the description must characterize results, and it does so minimally via "Each finding has a fix prompt." Combined with the readOnly annotation and full parameter coverage, an agent has enough to call it correctly and set expectations, despite no detail on finding structure or volume.

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?

One optional parameter with 100% schema description coverage, so the schema already explains `dir` and its default. The description adds nothing about path semantics (relative vs absolute, symlinks, monorepo subfolders), 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?

A specific verb plus resource ("Read a project folder") followed by an enumerated list of exactly what it detects: RLS policies with `true` conditions, tables without RLS, edge functions with verify_jwt=false, unverified Stripe webhooks, public-prefixed secrets, tracked .env, writable agent DB config. That makes it clearly a static in-repo audit, implicitly distinct from the other greenlit_* tools, though no sibling is named for direct contrast.

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?

Timing is stated ("before deploying") and a scope exclusion is given ("Pattern-based, not a full code review"), which tells the agent when this tool is the wrong choice. It stops short of naming greenlit_check or greenlit_advisor as the alternative for full review or external checks, so routing is partly left to inference.

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