AutEng MCP - Markdown Publishing & Document Share Links

auteng_docs_share

Share a document publicly. Returns a shareable URL.

Rate limited to 10 shares per wallet per day. 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 share (e.g. "reports/q1.md") visibility: Share visibility — only "public" in current version

Input Schema

TableJSON Schema

Name	Required	Default
`path`	Yes
`visibility`	No	public
`wallet_nonce`	Yes
`wallet_address`	Yes
`wallet_signature`	Yes
`wallet_timestamp`	Yes
`agent_display_name`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.8/5.0

Behavior5/5

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

No annotations are present, but the description discloses rate limiting (10 per day), EIP-191 signature requirement, and visibility constraint (only 'public'). This goes beyond the schema and provides crucial operational context.

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 compact with a brief introduction, rate limit and auth warnings, and a structured arg list. Every sentence serves a purpose.

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?

With an output schema present, the description doesn't need to explain return values. It covers auth, rate limits, and all parameter semantics, making it sufficiently complete for invocation.

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 has zero parameter descriptions, so the description fully compensates with detailed semantics: wallet fields specify format and purpose, path includes an example, and visibility notes allowed value. This adds significant meaning.

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?

Clearly states 'Share a document publicly' and notes it returns a shareable URL. Distinguishes from sibling tools (create, delete, list, recent, update, publish_markdown) through the specific 'share' action.

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?

Provides context of public sharing and references auteng_docs_create for auth details, implying how to set up authentication. Does not explicitly list when-not-to-use or alternative tools, but the purpose is clear enough.

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

All AutEng MCP - Markdown Publishing & Document Share Links tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

CRUD operations (create/update/delete/list) are clearly distinct, and share/recent have clear purposes. However, 'recent' could be confused with 'list' (workspace vs public feed), and 'publish_markdown' overlaps with create+share. Descriptions help clarify these boundaries, so most tools are unambiguous.

Naming Consistency3/5

The auteng_docs_* pattern holds for create/delete/list/share/update, but 'auteng_docs_recent' uses an adjective instead of a verb, and 'auteng_publish_markdown' breaks the pattern by using verb-first naming and omitting 'docs'. The mixed conventions are still readable but not fully consistent.

Tool Count5/5

Seven tools is well-scoped for a markdown publishing and document sharing server. Each tool earns its place covering CRUD, sharing, a public feed, and a publish shortcut, without redundancy or bloat.

Completeness4/5

The toolset covers the core lifecycle (create, update, delete, list) and sharing, but lacks a single-document get tool to retrieve content by path. This is a minor gap since list provides paths and update can be done with full content, so agents can work around it.

Resources

Need Help?