writ-mcp

Official

Overview Schema Source Related Servers Discussions Admin

writ_sandbox

Get a free 90-second sandbox grant to test a demo write: issue a live demo_write grant, run a check, and receive an ALLOW decision plus auth token for the verify-before-write flow. No API key needed.

Instructions

Get a free 90-second sandbox grant for a demo write. No API key needed.

Issues a live grant for verb "demo_write" on a target starting with "demo-", then runs writ_check so you get back an ALLOW decision plus auth token to practice the verify-before-write flow end to end.

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": {
      "sponsor_id": "<sponsor_id>",
      "agent_id": "<agent_id>",
      "target": "<target>",
      "purpose": "<purpose>"
    },
    "name": "writ_sandbox"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes
`purpose`	Yes
`agent_id`	Yes
`sponsor_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 2, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses the 90-second lifetime, that no API key is required, the exact verb restricted to it, the target prefix constraint, and that it auto-runs writ_check returning an ALLOW decision plus auth token. Only minor gaps remain around failure modes (e.g., what happens with a non-'demo-' target).

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?

The core value is front-loaded ('Get a free 90-second sandbox grant'), with supporting detail after. It is compact and every sentence adds information, though the second sentence packs several nested clauses.

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?

An output schema exists, so return contents need not be explained (the description still does, helpfully). However, for a 4-required-parameter tool at 0% schema coverage, three parameters have no semantics anywhere, leaving the agent unable to populate the call correctly.

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

Parameters2/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 define all four parameters. It only adds meaning for 'target' (must start with 'demo-'); sponsor_id, agent_id, and purpose are entirely unexplained in both schema and description.

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?

The description states a specific verb and resource: issue a 90-second sandbox grant for a 'demo_write' on a 'demo-' target. It implicitly separates itself from writ_grant by being the free, no-key practice path, though it never names that sibling explicitly.

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?

Usage context is implied: 'for a demo write' and 'to practice the verify-before-write flow end to end' suggest a sandbox/practice scenario. There is no explicit when-to-use versus the very similar writ_grant, and no when-not-to-use or prerequisites beyond the free/keyless note.

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