Skip to main content
Glama

report_limitation

Log blocked Zen browser tasks with the goal, what failed, and any workaround so developers can review and file GitHub issues.

Instructions

Tell the zenpilot developers about something you couldn't do in Zen with these tools.

Call it once per problem when a task needs something the tools lack (drag and drop, a
widget that ignores clicks, typing or select, content read_page doesn't show) or only
works after a workaround. goal: what you were trying to do, in a few words, like "pick a
date on a booking form". problem: what you tried and what happened, naming the elements, refs'
roles and errors. workaround: what worked instead, if anything. It's saved on the user's
computer for them to review and file as a GitHub issue, so leave out personal data and anything
the user typed.

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": {
      "goal": "<goal>",
      "problem": "<problem>"
    },
    "name": "report_limitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
problemYes
workaroundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the report is saved on the user's computer, that a human reviews it and may file it as a GitHub issue, and it warns against including personal data or user-typed content. The only gap is what the tool returns on success (confirmation, an ID, or nothing), which an agent would want to know before composing its next step.

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

Conciseness4/5

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

Purpose is front-loaded and the remaining sentences follow a logical order: when to call, then per-parameter guidance, then privacy constraint. It is a bit dense with the parenthetical example list plus per-parameter restatement, but nothing is genuinely wasteful for a tool whose value depends on getting good free-text input.

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 three-parameter, non-annotated, no-output-schema tool, the description covers what it does, when to fire it, how to fill each field, and the privacy boundary. Only the post-call behavior (return value / how the agent should proceed) is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: goal is defined with a concrete example ('pick a date on a booking form'), problem is defined as what was tried plus what happened with element names, refs' roles and errors, and workaround is defined as what worked instead, if anything. This adds real authoring guidance the bare string-typed schema cannot.

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 opening sentence names a specific verb and recipient — reporting a limitation back to the zenpilot developers — which is unmistakably different from every sibling (click, type, read_page, etc.). An agent can identify this as the escape hatch tool without opening the schema.

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

Usage Guidelines5/5

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

Usage is stated explicitly: 'Call it once per problem when a task needs something the tools lack... or only works after a workaround,' backed by concrete triggers (drag and drop, a widget that ignores clicks, content read_page doesn't show). The 'once per problem' clause also supplies de-duplication guidance, leaving little to inference.

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