Skip to main content
Glama

TesterSwap

Show or pause app

set_app_visibility
Idempotent

Show your app to new testers or pause it. Tests already started can finish.

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_id": "<app_id>",
      "visible": "<visible>"
    },
    "name": "set_app_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes
visibleYes

Output Schema

NameRequiredDescriptionDefault
app_idYes
visibleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this is a non-read-only, idempotent, non-destructive, closed-world mutation. The description adds genuinely non-obvious behavior beyond that: pausing does not abort tests already in progress. It stops short of covering permissions or whether pausing revokes access for existing testers.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and followed by the one caveat that matters. Nothing is redundant or padded.

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 two-parameter boolean toggle with an output schema present, the description covers the action, the scope, and the key side-effect on running tests. Return values need no explanation because the output schema exists.

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 coverage is 0%, so the schema gives only names and formats (app_id as UUID, visible as boolean). The description compensates partially by framing the operation as a show/pause binary, which conveys what visible=true vs false means, but it says nothing about app_id or about what pausing does to existing vs prospective testers beyond the in-flight note.

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 verb pair (show/pause) and the resource (the app, exposed to new testers), so the agent knows this toggles app visibility. It is distinguishable from lifecycle siblings like start_test or release_test, though it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Show your app to new testers or pause it' implies the toggle use case, and the second sentence clarifies scope for running tests. There is no explicit when-not guidance or reference to an alternative tool for related actions, so usage is implied rather than stated.

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.