Skip to main content
Glama

Get setup progress, integrations and feature status

get_setup_status
Read-only

Where this app has got to: the six setup steps and which are really done, worked out from data that has arrived, then the billing state, every Fictura feature toggle and whether it is on, and which third-party integrations (Stripe, RevenueCat, Slack, App Store Connect, …) are connected. Use it to check a setup step worked, and to check a feature is enabled before writing code that depends on it — a disabled tool is a server-side kill switch the SDK obeys.

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. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: completion is computed from arriving data rather than declared, and feature flags act as server-side kill switches the SDK honors. It does not discuss freshness, caching, or whether the aggregate is expensive to call, which matters for a status endpoint an agent may poll.

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 intent is front-loaded in the opening clause and the usage guidance follows in a separate sentence. The first sentence is long and enumerates four payload areas in a chain, which is dense but each element carries information. Nothing is redundant with the schema or annotations.

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 no input parameters and no output schema, the description must carry the return shape itself, and it does enumerate the four areas returned. It also explains the semantic weight of the feature toggles, which is the non-obvious part. Missing only operational details such as staleness or cost of calling, which are minor for a read-only status endpoint.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies the scope is the current app only, with no filtering arguments to explain.

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?

The description names a concrete resource and its contents: the six setup steps with their true completion state, billing state, every feature toggle, and connected third-party integrations. That is far more specific than the title, and the phrase 'worked out from data that has arrived' signals this is a derived status rather than a stored record. It stops short of naming how it differs from close siblings like get_setup_step or get_app_setup, so an agent still has to infer that split.

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 gives two explicit use cases: verify a setup step actually worked, and confirm a feature is enabled before writing dependent code, with the rationale that a disabled tool is a server-side kill switch the SDK obeys. That rationale is genuinely decision-shaping. There is no 'when not to use' or pointer to the single-step sibling for narrower needs.

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.

Resources