Skip to main content
Glama
Sign In

Gemmein

by com.gemmein
OverviewDiscussionsAdmin

Set where the app lives

set_app_lives
Idempotent

Sets whether the app lives on the web, as a mobile app, or both — read before go-live to shape which proofs it asks for (a web app's secret scan proves nothing about a phone bundle, so changing this clears any stored scan; go-live asks again). Before go-live it acts at once; once live, the founder approves it in the browser (request_app_lives).

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": {
      "lives": "<lives>"
    },
    "name": "set_app_lives"
  }
}

Input Schema

NameRequiredDescriptionDefault
livesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing a real side effect — changing the setting clears any stored scan because a web scan proves nothing about a phone bundle — plus the timing split between immediate effect pre-go-live and founder approval post-go-live. Note the clearing of stored scans sits in mild tension with destructiveHint=false, but the description is the truthful source here rather than contradicting the annotation.

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?

Front-loaded with the core action and value set, then the side effect, then the approval workflow — good ordering with no filler. It is dense and parenthetical, requiring a careful read, which keeps it off a 5.

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?

For a one-param, no-output-schema setter, the description covers purpose, side effects, idempotency implications, and the approval path. Nothing an agent needs in order to call it correctly or warn the user is missing.

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?

Schema coverage is 0% and the single parameter is an enum, but the description restates the enum's meaning in prose ('on the web, as a mobile app, or both'), so the agent understands the value space without the schema. It adds no format or edge-case detail beyond that, so not a 5.

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?

States a specific verb and resource: it sets whether the app lives on web, mobile, or both, and enumerates the exact values. It also names the sibling it is not (request_app_lives) and explains the difference, so an agent can route without opening either 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?

Gives an explicit 'when': read/use before go-live to shape which proofs are requested, and explains the branch once the app is live (founder approves in browser via request_app_lives). The alternative tool and the condition selecting it are both spelled out.

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

All Gemmein toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources