Skip to main content
Glama

greenlit_advisor

Read-only

Convert Supabase security or performance advisor lints into plain-English findings with a fix prompt for each issue, ordered worst first.

Instructions

Turn Supabase's Security or Performance Advisor results into plain-English findings with a fix prompt for each, worst first. Get the results from the Supabase MCP server's get_advisors tool (type "security") for the user's project, then pass them here as lints. This is the reliable way to learn which rules are too loose and whether strangers can change or delete data, which no outside check can see.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lints": "<lints>"
    },
    "name": "greenlit_advisor"
  }
}

Input Schema

NameRequiredDescriptionDefault
lintsYesThe advisor output: a list of lints, or the object that contains one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile; the description adds useful context beyond it — the output is plain-English findings with a per-lint fix prompt, ordered worst-first, and it explains the analytical value (which rules are too loose, whether data can be altered). It does not cover failure modes (e.g., what happens on malformed or non-security lint input) or any limits, so not a 5.

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 core transformation before the sourcing instruction. The closing sentence about being the "reliable way" to see rule looseness is persuasive framing rather than operational detail, but it is short and does convey scope of insight.

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 one required parameter, no output schema, and a read-only annotation, the description covers what an agent needs: input source, input form, and what comes back. Only minor gaps remain, such as behavior on empty or non-security lint payloads.

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 schema already allows either a list of lints or the containing object. The description still adds real meaning by identifying where that value comes from (get_advisors, type "security"), which the schema cannot express.

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?

A specific verb and resource: turns Supabase Security/Performance Advisor results into plain-English findings with a fix prompt per issue, ordered worst first. The transformation is unambiguous and distinct from generic schema/query siblings, and the output shape is stated up front.

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 states the prerequisite pipeline: fetch results via get_advisors with type "security" for the user's project, then pass them here as `lints`. That names the source tool, the required argument variant, and the hand-off point, leaving little to infer.

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