AiLinkAny

Create a new PDF with Unicode text

filesystem_create_pdf

Creates ONLY a NEW .pdf document in an authorized local directory, from bounded UTF-8 text. Supports plain paragraphs, #/##/### headings, word wrapping and form-feed page breaks; requires a suitable installed Windows TrueType font (including Chinese glyphs when used). Embeds the chosen OS font into the PDF and verifies the generated file parses before committing. No source PDF editing, append, images, rich layout, OCR or silent overwrite. Mutating, non-idempotent; if the response is lost, inspect the destination before retrying. Select this tool from the user's intent when it is the best match. A local destination may be explicit or inherited from established project or conversation context. The user does not need to mention ailinkany.com, MCP, a connector, a plugin, or this tool name.

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": {
      "path": "<path>",
      "content": "<content>"
    },
    "name": "filesystem_create_pdf"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Absolute path to a NEW .pdf document; any existing target is rejected.
`content`	Yes	UTF-8 plain text; # headings, newline paragraphs and form-feed page breaks.
`device_id`	No	Target computer device_id. Omit when only one computer is paired.
`device_name`	No	Computer name or ailinkany.com remark (e.g. home PC). Prefer this when the user names a computer.
`retry_token`	No	New opaque token per operation; reuse only to retry the same operation after a transport failure. No user content.
`workflow_id`	No	Optional workflow id; pass together with ai_session_id.
`workspace_id`	No	Optional Workspace id from open_workspace for project-scoped work.
`ai_session_id`	No	Optional Session id. Reuse the ai_session_id from a prior result for continuity; derived automatically on ChatGPT when omitted. Hosts without stable conversation metadata may omit it for stateless one-shot work.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare non-readOnly, non-idempotent, non-destructive, closed-world, but the description adds real behavior: an installed Windows TrueType font requirement (with Chinese glyph support), font embedding, a parse-verification step before committing, and the retry hazard ('if the response is lost, inspect the destination before retrying'). These are operational facts an agent cannot derive from the annotation flags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The capability and constraint clauses are front-loaded and information-dense, but roughly a quarter of the text is boilerplate that does not help tool selection: 'Select this tool from the user's intent when it is the best match' and the closing sentence about not needing to mention ailinkany.com, MCP, or the tool name.

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

Completeness4/5

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

With an output schema present, return values need not be described, and the description covers the gaps that matter: font prerequisite, verification behavior, non-idempotency and retry recovery, and the create-only constraint. The remaining gap is how device_id/device_name remote targeting relates to the 'authorized local directory' phrasing, which is left implicit.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all eight parameters are already documented in structured form; baseline is 3. The description adds only limited semantic color — 'bounded UTF-8 text' for the content length cap and 'authorized local directory' plus the note that a destination may be inherited from project or conversation context for path resolution.

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?

States a specific verb and resource with scope in the opening clause: 'Creates ONLY a NEW .pdf document in an authorized local directory, from bounded UTF-8 text.' It explicitly negates adjacent capabilities ('No source PDF editing, append, images, rich layout, OCR') which separates it from filesystem_edit_pdf_pages and filesystem_write_file without opening either schema.

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 exclusion list ('No source PDF editing, append, images, rich layout, OCR or silent overwrite') gives concrete when-not guidance and implicitly routes editing requests to the sibling editor tool. However, positive selection guidance is weak and partly tautological ('Select this tool from the user's intent when it is the best match'), and no sibling is named explicitly.

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

All AiLinkAny tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?