Skip to main content
Glama

Get Setup Status

get_setup_status
Read-onlyIdempotent

Check where a user's Maestro setup stands: AI key, writer mode, demo bases, completed steps and the next setup step to run, so an agent can start fresh.

Instructions

Where this user's Maestro setup stands, for an agent starting fresh. Returns ai_key (whether Maestro has its own AI key), writer (who writes for agent apps: "agent", the default, means the agent app writes, so the tools where Maestro's own AI writes the text refuse (409) and the agent writes it and saves it with the matching store or add tool; "maestro" means Maestro's AI writes it with the user's key, which needs ai_key), demo_bases (slugs of the shipped demo resume, never the user's own), next_step (the first setup step an agent can do that is not done, {step, tool_set, says}; null when none is left), tool_sets (each set's name, use_when and holds, in journey order) and steps (the full setup status: each step's done and detail, form-answer readiness with autofill.chosen, false while the user has not chosen where they apply, so no country's questions count, and autofill.home_pay, the pay of the country they live in, counted beside the groups and saved as preferences.desired_salary; suggested bases, PDF engines). The AI key, the writer and the default resume design are set by the user in the app and are never a next step.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes further with genuinely non-obvious behavior: several tools refuse with 409 when writer='agent', 'maestro' mode requires ai_key, and autofill.chosen=false means no country's questions count. That is substantial context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only two sentences, and almost every clause carries real information, but the second is a single sprawling run-on with nested parentheses and semicolon chains that is hard to parse in one read. The purpose is front-loaded, yet the return-field semantics would be far more usable as a structured list.

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?

With no output schema and no parameters, the description carries the full burden of explaining the return payload, and it does so field by field (ai_key, writer, demo_bases, next_step, tool_sets, steps with autofill.chosen, home_pay, preferences.desired_salary). An agent can interpret every returned key without additional guidance.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is an empty object and the description correctly implies no inputs are needed.

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?

Opens by stating the resource and scope: 'Where this user's Maestro setup stands, for an agent starting fresh.' This is a recognizable setup-state reader distinct from the data-centric get_* siblings, though the purpose sentence is immediately swallowed by a dense enumeration of return fields rather than a crisp verb-first statement.

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?

The phrase 'for an agent starting fresh' establishes the use case (session start / orientation) and the next_step field tells the agent what to do afterward. It also rules out a class of actions ('never a next step'), but it names no sibling alternative and gives no explicit when-not condition.

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

Deploy Server

Other Tools