Skip to main content
Glama

Set up Prometheor and show the tour

setup
Idempotent

Sets Prometheor up in the app you run in and shows the owner what it can do. Use it when the owner asks to set Prometheor up or to connect this project, bot or agent ("Set up Prometheor." or "Connect yourself to Prometheor.", in any language) or asks what Prometheor can do or for its tour ("Show me the Prometheor tour."; then pass tour_only). The answer has setup (the steps for your app, such as keeping the owner's Prometheor rule, connecting this chat's project or taking tasks as a cloud AI) and tour (what the owner's AIs can do together now, which of them are connected, what is still to connect, and things to try). It changes no setting by itself: the steps are yours to do, and the owner's request for the setup is what allows them.

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": {
      "app": "<app>"
    },
    "name": "setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe app you run in: claude (a claude.ai chat or project), claude_code, chatgpt, codex, cursor, grok_bot, cloud_ai (another AI that runs in its own cloud and can be woken there), or other.
tour_onlyNoOnly the tour, without the setup steps.
plugin_checkNoOnly the plugin check, without the setup steps and the tour: what a Prometheor plugin's skill asks for once per chat.
plugin_versionNoOnly when a Prometheor plugin's skill told you its version: that version, as it is written there. The answer's plugin part says whether a newer one exists and how your app gets it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / plugin_check
      Added value: +{
      +  "const": true,
      +  "description": "Only the plugin check, without the setup steps and the tour: what a Prometheor plugin's skill asks for once per chat.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / plugin_version
      Added value: +{
      +  "description": "Only when a Prometheor plugin's skill told you its version: that version, as it is written there. The answer's plugin part says whether a newer one exists and how your app gets it.",
      +  "maxLength": 20,
      +  "type": "string"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, and the description adds the important behavioral fact that the tool changes no setting by itself because the steps are the agent's to perform, plus the authorization framing that the owner's request is what permits the setup. The one tension is that "it changes no setting by itself" reads close to read-only while readOnlyHint is false, but the two can coexist for a tool that records state rather than applying settings, so this is not a clear contradiction.

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?

It is front-loaded with purpose and then triggers, and every sentence carries information about scope, return contents, or side effects. It is dense with parenthetical example phrases, but those examples are functional rather than filler.

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 four-parameter tool with no output schema, it explains the response shape (setup steps and tour contents), the side-effect profile, and the trigger conditions. The gap is that the plugin_check mode, a distinct behavior of the same tool, is never described in prose.

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 enum values, tour_only, plugin_check and plugin_version are already documented in the schema. The description adds only a little beyond that, explaining that tour_only yields the tour without setup steps and that the plugin part reports whether a newer version exists, while never mentioning plugin_check.

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 opens with a specific verb and resource ("Sets Prometheor up in the app you run in") and adds a second capability (showing the tour), so an agent can tell this apart from siblings such as worker_setup or settings 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the exact owner phrasings that should trigger the tool ("Set up Prometheor.", "Connect yourself to Prometheor.", in any language) and explicitly routes the tour-only case to the tour_only parameter, which is real when-to-use guidance rather than inference.

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