Skip to main content
Glama
Sign In
wardogs-mcp

wardogs-mcp

by MudcrabWarrior
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_readback

Read the current builder manifest, totals, status line, and sign-in state to verify layout details without modifying anything. Get a snapshot of the current state for validation and rendering.

Instructions

Read the builder's manifest, totals, status line and sign-in state without changing anything.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly guarantees 'without changing anything', which is a significant behavioral disclosure for a read tool, and it names the exact data areas returned.

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 sentence with no filler. The verb is front-loaded and every element in the list earns its place.

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 zero-parameter read-only tool with no output schema, the description names all relevant state categories and the side-effect guarantee. A return-format note would be nice, but it is not essential for invoking this tool correctly.

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?

The tool has zero parameters, so there are no parameter semantics for the schema to provide. The description correctly focuses on the read payload rather than inputs.

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 uses the specific verb 'Read' and enumerates exact resources: manifest, totals, status line, and sign-in state. The 'without changing anything' clause makes its read-only nature explicit and distinguishes it from mutating siblings.

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?

The description implies use when the agent needs to inspect builder state without side effects, but it does not explicitly state when to choose this tool over sibling read tools like browser_screenshot or data_refresh. No alternatives or exclusions are mentioned.

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