This post was drafted with AI assistance and reviewed by the PerfectVector team.
An MCP tool that produces a file needs a clear delivery contract: how the user retrieves the file, how long access lasts, and who can use the link. We build an image-to-SVG MCP server, and its public docs describe such a contract. Below are seven rules from it, each with the behavior the docs state as of 2026-11-13. Everything here is client-visible behavior from the docs, not a description of our server's internals.
1. Return a reference with an expiry, not the file. The delivered SVG comes back as a download link that works for 24 hours. While the SVG is still stored, an expired link can be replaced for free; once it's gone, the tool says it's unavailable and doesn't start a new paid conversion. The file itself is kept for about 30 days after upload.
2. Remember the link is a bearer secret. Anyone with the link can download that SVG until it expires, and it keeps working after you disconnect the assistant, unless the PerfectVector account is deleted first. The docs say so in plain words ("share it only as you would share the file"). If your tool does the same, say it where users will read it.
3. Let the assistant read small results. The assistant can read a delivered SVG's text to keep working with it (recolor it, animate it, embed it), up to about 2 MB. Larger files are download-only. For your own tool, document the inline-read limit and the download fallback.
4. Make input flexible, because chat clients differ. The same tool accepts an image four ways: a public https:// link to the image file itself (fetched without your cookies), an attachment in ChatGPT, a file chosen in a card inside Claude, and a local path an agent such as Claude Code can upload itself. Limits apply to all four: PNG, JPEG or WebP, up to 5 MB, 100–4,096 px per side.
5. Put a free price check before the paid step. The tool prices the request first (free), and conversion needs authorization first: an answer in the chat, a permission you grant in the app, or choosing a file in the card. If you've set an app to always allow the step, it can start without a new prompt. If nobody answers within 30 minutes, the request expires, the uploaded image is deleted, and no credit is used. Whether the question comes from the assistant or the client's permission dialog depends on the client; the docs list which defaults each one uses.
6. Make re-fetching safe. "Get my last SVG" returns the file already made. It does not start a new paid request, and continuing a conversion that is still processing never charges twice. A new request for the same image is a new request, and it is charged again.
7. Say what you can't do. The tool converts with standard settings and has no controls for detail, colors or background removal. If you want a different result, edit the image first. Documenting the limit also keeps the assistant from promising knobs that don't exist.
None of this is specific to SVGs. Any tool that takes a file and returns a file can reuse the seven: an expiring reference, a stated sharing model, an inline-read limit, several input paths, a free price check before a paid step, a re-fetch that doesn't start new work, and documented limits.
Reference: PerfectVector MCP credits and downloads.
We build PerfectVector, an image-to-vector tool.
Top comments (0)