Skip to main content
Glama

Writ tool reference

writ_help
Read-onlyIdempotent

The full reference of any Writ tool (every parameter and its rules) and the complete guide. topic = a tool name (e.g. 'writ_browser_compose', a 'run_' tool), 'guide' for the manual (recurring digests, HTTP flow building, buying on a price, crawl modes), 'actions' / 'recording' / '2fa' for the browser rules, 'http_flows' / 'flow_operators' for writing an HTTP flow, or empty for the list of topics.

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

Input Schema

NameRequiredDescriptionDefault
topicNoA tool name, 'guide', 'actions', 'recording', '2fa', 'http_flows', 'flow_operators', or empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"A tool name, 'guide', 'actions', 'recording', '2fa', or empty."New value: +"A tool name, 'guide', 'actions', 'recording', '2fa', 'http_flows', 'flow_operators', or empty."
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the response contains every parameter and its rules plus a guide, but says nothing about output format, size, or what happens with an unrecognized topic.

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 in the first clause, then the topic options follow. The single dense sentence with stacked parentheticals is readable but slightly run-on; a short bulleted topic list would scan faster.

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 one-optional-parameter documentation tool with no output schema, the definition covers the topic space thoroughly. Minor gaps: behavior on an invalid topic and the shape/format of the returned reference.

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?

Schema coverage is 100% and the schema already lists the accepted values, but the description goes further by explaining what 'guide' actually contains (recurring digests, HTTP flow building, buying on a price, crawl modes) and that an empty value yields the topic list. That is real meaning added beyond the schema.

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 concretely that it returns 'the full reference of any Writ tool (every parameter and its rules) and the complete guide' — a specific retrieval verb plus the resource. It is clearly not an action tool like its siblings, though it never explicitly contrasts itself with them.

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 topic enumeration effectively tells the agent which value selects which content ('guide' for the manual, 'actions'/'recording'/'2fa' for browser rules, empty for the topic list). What's missing is a direct instruction on when to call this at all, e.g. before invoking an unfamiliar writ_* tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.