Skip to main content
Glama

Plures

Get an app's setup plan

get_setup_plan
Read-only

Returns what it takes to set an app up in this project, as instructions you can follow: the checks the developer turned on and where each goes in the code, the line that sends outputs to be graded, and the line that logs answers. It is the same plan npx plures init shows. Reading it changes nothing. Tell the user what you are about to change before you edit their code.

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

Input Schema

NameRequiredDescriptionDefault
appNoThe app id. Default: PLURES_APP, then the default app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description reinforces the readOnlyHint annotation with the plain statement 'Reading it changes nothing', and discloses the openWorldHint-adjacent behavior that it mirrors the CLI plan. It adds a useful operational norm (announce changes before mutating code). It does not cover error behavior or the default-app resolution if the app is unavailable.

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 front-loaded with the return payload and then tacks on context and a usage norm, with little wasted wording. The trailing instruction about telling the user is slightly tangential to describing the tool but still earns its place as behavioral guidance.

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 simple, read-only, single-optional-parameter tool with no output schema, the description does the heavy lifting by describing the returned plan's contents in concrete terms. It is nearly complete; only default-app edge behavior and failure cases are left implicit.

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?

Schema description coverage is 100%, so the single `app` parameter is already fully documented in the schema, including its default chain. The description adds no additional meaning about the parameter beyond the structured schema, making the baseline 3 appropriate.

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 names a specific verb and resource ('Returns what it takes to set an app up in this project') and enumerates the payload contents: enabled checks and their placement, the grading-output line, and the answer-logging line. An agent can distinguish this setup-plan tool from siblings like get_improve_plan or get_audit_report without opening a schema.

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?

It implies the usage context clearly: read the plan before editing code and warn the user first ('Tell the user what you are about to change before you edit their code'). It also anchors it to `npx plures init`, giving a practical reference point. There is no explicit when-not or named alternative, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.