Skip to main content
Glama

Einrichtungsstand für die Karte lesen

setup_status_app
Read-only

App-only, für die FrankKi-Übergabe-Karte im Chat: die Karte pollt hier den aktuellen Einrichtungsstand und merkt so selbst, wenn der Mensch aus dem Browser zurück ist. Für Agenten liefert mcp_health denselben Stand unter setup. EN: App-only, for the FrankKi handover card in the chat: the card polls the current setup state here and so notices by itself when the human is back from the browser. Agents get the same state from mcp_health under setup.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/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 useful context that this is a polling endpoint for an app card and that the same state is exposed via mcp_health.setup, though it does not spell out return details beyond that.

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 German and English versions are front-loaded and clear, but the English text largely repeats the German text rather than adding new information. It remains efficient for a bilingual description, with only mild redundancy.

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?

Given zero parameters, no output schema, and annotations covering safety, the definition is nearly complete. It explains the app-only polling context and points agents to mcp_health for the same setup state, though it does not describe the setup payload structure itself.

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?

There are no input parameters and the schema is empty, so there is no parameter meaning for the description to add. The baseline for a zero-parameter tool is therefore met.

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 states a specific resource and action: polling/reading the current setup state for the FrankKi handover card. It also explicitly distinguishes the tool from the sibling mcp_health by saying agents should get the same state there under setup.

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?

It says 'App-only' and names the concrete caller, the handover card in chat, so the intended use case is explicit. It also routes agents to mcp_health, giving a clear alternative when this app-only path is not the right one.

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.