Skip to main content
Glama
Sign In
wardogs-mcp

wardogs-mcp

by MudcrabWarrior
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_key

Press keyboard shortcuts in the WARDOGS base builder to switch camera views, frame elements, cycle tabs, and toggle overlays, enabling direct layout control.

Instructions

Press a key in the builder (camera 1-4, F frame, Tab cycle, Z/V toggles).

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": {
      "key": "<key>"
    },
    "name": "browser_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It identifies the action and some effects ('toggles,' 'cycle'), but does not specify return values, whether the builder must be open/focused, whether key presses are asynchronous, or whether toggles persist.

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?

A single front-loaded sentence with parenthetical examples and no filler. Every word contributes to defining the action and key inputs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but with no output schema, no parameter descriptions, and no annotations, the description should provide more detail. It covers common key examples but does not enumerate all valid keys or state preconditions like having the builder open and focused.

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?

The schema gives only a 'key' string with no description or enums (0% coverage), so the description must compensate. It adds useful examples such as camera 1-4, F, Tab, Z/V, but these are illustrative rather than an exact or exhaustive list, leaving ambiguity about accepted syntax and case sensitivity.

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: 'Press a key in the builder.' The parenthetical examples (camera 1-4, F frame, Tab cycle, Z/V toggles) make the tool's scope concrete and distinguish it from sibling browser_* tools like browser_open, browser_screenshot, or browser_readback.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives, nor any exclusions or prerequisites. The only context is 'in the builder,' which is implied rather than explicit.

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