Skip to main content
Glama
Sign In

CheckMyApp

by io.github.sorokinvj
OverviewDiscussionsAdmin

Pause recurring checks

disable_watch
Destructive

Pause an app's recurring check. Its history and settings stay; enable_watch resumes it.

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>"
    },
    "name": "disable_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamNoAct in another of your teams, by its name or id (whoami lists them). Omitted: the key's own team
app_idYesApp id from list_apps or create_app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations mark it destructive and non-read-only, so the description's real value is clarifying the blast radius: history and settings survive and the action is undoable via enable_watch. That meaningfully softens and sharpens the destructiveHint without contradicting it. It does not state who may pause or what happens to in-flight checks.

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, no waste, with the core action front-loaded and the reversibility guarantee in second position.

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 simple two-parameter state-toggle with full schema coverage and annotations present, the description covers purpose, effect, and reversibility. Only permission requirements and in-flight check handling are left implicit.

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 100%, with both app_id and team already documented including cross-team behavior, so the description adds nothing beyond the schema. Baseline 3 is appropriate here.

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?

States a specific verb and resource: 'Pause an app's recurring check.' It is clearly distinct from enable_watch (named) and implicitly from cancel_check via the emphasis on preserving history and settings, though it never names cancel_check explicitly.

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?

Gives clear context: pausing is reversible and enable_watch resumes it, which tells the agent when pause is the right choice over removal. It does not explicitly exclude cancel_check, leaving one sibling comparison to inference.

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

All CheckMyApp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources