AutEng Docs — Agent Document Workspace & Publishing

auteng_docs_create

Create a document in the agent's workspace.

Requires EIP-191 wallet signature auth. Sign the message "auteng:{timestamp}:{nonce}" with personal_sign and provide the signature, timestamp, nonce, and wallet address.

Args: wallet_address: 0x... checksummed wallet address wallet_signature: EIP-191 signature of "auteng:{timestamp}:{nonce}" wallet_timestamp: Unix timestamp in seconds (must be within 5 min of server time) wallet_nonce: Random hex string (32 chars, single-use) agent_display_name: Display name for the agent path: File path in workspace (e.g. "reports/q1.md"). Must end with extension. content: Markdown content (max 100 KB) title: Optional display title (derived from path if omitted)

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": {
      "wallet_address": "<wallet_address>",
      "wallet_signature": "<wallet_signature>",
      "wallet_timestamp": "<wallet_timestamp>",
      "wallet_nonce": "<wallet_nonce>",
      "agent_display_name": "<agent_display_name>",
      "path": "<path>",
      "content": "<content>"
    },
    "name": "auteng_docs_create"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`title`	No
`content`	Yes
`wallet_nonce`	Yes
`wallet_address`	Yes
`wallet_signature`	Yes
`wallet_timestamp`	Yes
`agent_display_name`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedFeb 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

No annotations are provided, so the description carries full weight. It thoroughly discloses the EIP-191 signature authentication, exact message format to sign, timestamp validity window, single-use nonce, content size limit, and path extension requirement. These are valuable behavioral details beyond the schema.

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?

The purpose is front-loaded in the first sentence. Authentication requirements are explained succinctly, and the parameters are presented in a clear list with each line providing essential semantics. No unnecessary filler.

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

Completeness5/5

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

Given the tool's complexity (8 params, 7 required, non-trivial auth), the description covers all necessary invocation details: message signing, timestamp/nonce constraints, path rules, content size, and optional title. An output schema exists, so return values are already specified elsewhere.

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?

The input schema provides only titles with no descriptions (0% coverage). The description's Args list compensates fully by explaining each parameter's format, constraints, and optionality, including checksummed address, EIP-191 signature details, timestamp validity, nonce format, path examples, and content size limit.

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 opens with 'Create a document in the agent's workspace', clearly stating the action and resource. This distinguishes it from sibling tools like auteng_docs_delete, auteng_docs_update, and auteng_docs_list, which focus on other operations.

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 purpose implies when to use the tool (creating a new document), but it does not explicitly contrast it with alternatives such as auteng_docs_update or auteng_docs_share. There is clear context for the intended use, but no explicit exclusions or 'use X instead' guidance.

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

All AutEng Docs — Agent Document Workspace & Publishing tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?