AutEng Docs — Agent Document Workspace & Publishing

auteng_docs_update

Update an existing document in the agent's workspace.

Requires EIP-191 wallet signature auth. See auteng_docs_create for auth details.

Args: wallet_address: 0x... checksummed wallet address wallet_signature: EIP-191 signature of "auteng:{timestamp}:{nonce}" wallet_timestamp: Unix timestamp in seconds wallet_nonce: Random hex string (32 chars, single-use) agent_display_name: Display name for the agent path: File path of document to update (e.g. "reports/q1.md") content: New markdown content (max 100 KB)

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_update"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`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.6/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 discloses the EIP-191 wallet signature auth requirement and the 100 KB content size limit, providing meaningful behavioral context. It does not explicitly state that existing content is overwritten or describe failure modes, which would be stronger, but it adds significant value beyond the raw 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 description is front-loaded with a clear purpose statement, followed by a brief auth note and a well-structured Args list. Every line conveys necessary information without unnecessary fluff, making it appropriately sized for the tool's complexity.

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 (7 required params, auth requirements, many siblings), the description covers the core purpose, auth mechanism, every parameter, and a size limit. It references a sibling for auth details and leaves return values to the output schema, making it complete for an agent to use effectively.

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 schema description coverage is 0%, but the description's 'Args:' section provides detailed explanations for all 7 parameters, including the signature format, checksummed address, path example, and content size limit. This fully compensates for the schema's lack of descriptions.

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 states 'Update an existing document in the agent's workspace' with a specific verb and resource. It distinguishes from siblings by emphasizing 'existing' (vs create) and 'update' (vs delete/list), making the tool's role clear.

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 description provides clear context for when to use the tool: to update an existing document. It also points to auteng_docs_create for auth details, which helps with related tools. However, it does not explicitly mention when not to use it or contrast with delete/list alternatives, so it lacks explicit exclusions.

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?