Scribe Mail

Create an asset

create_asset

Upload an image to the workspace's asset library. Provide EITHER file_base64 (+ filename) OR source_url — exactly one. For a file the user uploaded in chat (no public URL), send its bytes as file_base64; if you cannot read the raw bytes on this platform, ask the user for a hosted URL or reuse an existing asset from list_assets instead of guessing. Non-images, bad base64, oversized files (>15MB), or a disallowed URL return 422.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Display name (defaults to the filename).
`role`	No	Optional role: company_logo, profile_picture, or banner.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`filename`	No	Original filename (required when `file_base64` is given).
`source_url`	No	Public http(s) URL the server downloads the image from (alternative to file_base64). Redirects ARE followed (each hop re-checked); hosts resolving to private/loopback addresses are blocked. If a fetch fails (some hosts block server-side downloads), pass the bytes as `file_base64` instead.
`file_base64`	No	Base64-encoded image bytes. Provide WITH `filename`, or use `source_url` instead. A `data:` URI, line-wrapped base64, or base64url is accepted as-is — the server unwraps it, so pass whatever your file-reading helper returned without re-encoding.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (not read-only, open-world, not idempotent). The description adds valuable behavioral context beyond them: the 15MB size limit, and the specific failure modes (non-image, malformed base64, disallowed URL) that return a 422. This meaningfully helps an agent anticipate and handle errors.

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

Conciseness4/5

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

Purpose is front-loaded, then the input-mode rule, then error handling — a logical progression. Every sentence carries information (mode selection, fallback guidance, error conditions), though the final sentence is dense with edge cases.

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?

Return values are covered by the output schema, so the description need not explain them. For an upload tool with multiple input modes and several failure paths, the description supplies exactly the context needed to invoke it correctly: which argument to use when, size/type limits, and fallback behavior.

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 the schema already documents every parameter in detail. The description reinforces the mutual-exclusivity rule ('exactly one' of file_base64 or source_url) and the filename pairing, but this largely restates what the schema already provides. Baseline 3 is appropriate when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: 'Upload an image to the workspace's asset library.' It is unambiguous what the tool does. However, it does not explicitly contrast its purpose against the create/update/delete_asset siblings — the named alternative (list_assets) is invoked for reuse rather than for purpose differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit conditions and alternatives: use file_base64 for a chat-uploaded file with no public URL, ask for a hosted URL or reuse from list_assets if raw bytes can't be read, and it warns against guessing. When-to-use and when-not-to-use are both covered.

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

All Scribe Mail 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.