Skip to main content
Glama
Sign In
Tap

Tap

by LeonTing1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

tap_env

Read-onlyIdempotent

Check runtime environment: binary version, TAP_HOME, skills count, Playwright availability, daemon status, OS info. Zero side effects, no browser needed. Use for troubleshooting or CI health gates.

Instructions

Check tap runtime environment: binary version, TAP_HOME directory, installed skills count, Playwright availability, daemon status, and OS info. Zero side effects — no browser needed. Use for initial troubleshooting or CI health gates.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.15.14
  2. Removedv0.15.8
  3. Addedv0.1.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide safety hints (readOnlyHint, destructiveHint, idempotentHint). The description adds 'Zero side effects — no browser needed,' reinforcing and adding context beyond annotations.

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 sentences, front-loaded with main purpose, then usage guidance. No redundant or unnecessary information.

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?

Given no parameters, no output schema, but rich annotations, the description is complete: it explains what the tool checks and when to use it. No missing context.

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?

No parameters exist, and schema coverage is 100% (trivial). Per guidelines, 0 parameters baseline is 4; description does not need to add parameter meaning.

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 clearly states the tool checks tap runtime environment, listing specific items (binary version, TAP_HOME, skills count, etc.) and explicitly distinguishes from siblings by noting zero side effects and no browser needed.

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?

The description says 'Use for initial troubleshooting or CI health gates,' providing clear context. While it doesn't explicitly mention when not to use or alternative tools, the purpose is well-defined among siblings.

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

Deploy Server

Other Tools