Renders the current state of a live Trident document as a PNG image directly from the Yjs collaborative session — bypassing Firestore, which may be stale. Returns a base64-encoded PNG. Use this to visually verify that diagram edits look correct before or after making changes.
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | Access token for this document. The document ID is embedded in the token. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, and the description adds valuable context about the data source (Yjs session vs Firestore), the bypassing behavior, and the return format (base64-encoded PNG). This goes beyond the annotations and helps the agent understand the tool's freshness promises.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core action and output format. The usage guidance is succinct and relevant, with no wasted words or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple tool with one parameter, no output schema, and clear annotations. The description covers the core functionality, the return format, and the intended use case, making it sufficient for an agent to select and call the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a clear description of the token parameter. The description adds no extra parameter semantics, but this is acceptable since the schema already explains the token's role and document ID embedding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Renders' with a clear resource ('live Trident document') and specifies the output ('PNG image'). It distinguishes itself from sibling tools like get_document_summary by emphasizing visual rendering from the live Yjs session.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states the intended use case: 'Use this to visually verify that diagram edits look correct before or after making changes.' It also provides rationale for choosing this over Firestore-backed approaches by noting Firestore may be stale. However, it does not name alternative tools or explicitly state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.