Skip to main content
Glama

xi.pe

by pe.xi
OverviewDiscussionsAdmin

Create a paste

create_paste

Store UTF-8 text at xi.pe and get back a short URL anyone can read. Use it when text has to leave the conversation: someone asks for a shareable link to text you already have -- 'share this', 'give me a URL for it'; something a human needs to read would flood the chat inline -- a long diff, a stack trace, a generated config, a report; or something has to reach another agent, session or machine that does not share your filesystem. Maximum 2 MiB (2,097,152 bytes); larger is rejected, not truncated. Returns url, code, delete_token, size and expires. The delete_token is shown once and is the only way to delete the paste -- pass it to the user verbatim if a human is in the loop. If you are outputting markdown for human reading, highly consider adding ?md to the link you hand back to make it more readable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ttlNohow long the paste should live: a number followed by m, h or d (for example 30m, 6h, 3d). Defaults to the 7 day maximum. Cannot be longer than 7d.
longNouse a 23-character code instead of the default 6. Worth it when a lucky guess would actually matter -- credentials, private logs, anything with real consequences if a stranger landed on it.
contentYesthe UTF-8 text to store. Maximum 2 MiB (2,097,152 bytes), counted as UTF-8 bytes rather than characters. Oversize is rejected with no truncation. No line-length or line-count limit.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesthe URL of the new paste
codeYesthe paste's code
sizeYesstored size in bytes
expiresYesRFC 3339 timestamp after which the paste is gone
delete_tokenYesthe only capability that can delete this paste. Shown once -- surface it verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / long / description
      Previous value: -"use a 23-character code instead of the default 6. Use it when the link itself is the only thing keeping the paste private."New value: +"use a 23-character code instead of the default 6. Worth it when a lucky guess would actually matter -- credentials, private logs, anything with real consequences if a stranger landed on it."
  2. Changed1 schema field changed
    • changedInput schema / properties / long / description
      Previous value: -"use a long unguessable code (23 characters) instead of the default 4-5. Use this when the URL itself is the secret: a 4-5 character code is guessable by anyone enumerating; 23 characters is not."New value: +"use a 23-character code instead of the default 6. Use it when the link itself is the only thing keeping the paste private."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations all set to false, the description carries the full burden of behavioral disclosure. It states the 2 MiB limit and that oversized input is rejected (not truncated), mentions that the delete_token appears once and is the only deletion mechanism, and specifies the returned fields. This covers key operational behavior an agent needs.

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 yet complete. It front-loads the core purpose, bundles use-case triggers, then covers size limits, return values, and the delete-token special case, and ends with a markdown-readability tip. Every sentence adds value with no padding, and the structure logically flows from purpose to practical usage.

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?

Given the tool's moderate complexity (3 parameters, 1 required) and the presence of an output schema, the description covers everything an agent needs: what to store, size policy, when to use it, return fields, the one-time delete token, and a formatting tip. No critical operational detail is missing.

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% – every parameter (content, ttl, long) has a clear description including defaults and constraints. The tool description adds no extra parameter-specific meaning beyond what is already in the schema; it reiterates size limits and mentions the TTL default, but these are already documented. Since the schema is comprehensive, a baseline of 3 is appropriate.

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?

The description opens with a specific verb and resource (Store UTF-8 text at xi.pe and get back a short URL), clearly distinguishing the action from its sibling tools (read_paste and delete_paste). It also states the output format (url, code, delete_token, size, expires), making the tool's purpose unmistakable.

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?

The description explicitly lists concrete triggers ('share this', 'give me a URL for it'), conditional cases (long diffs, stack traces, configs, reports that would flood chat), and cross-context needs (another agent/session/machine without shared filesystem). It also advises on handling the delete_token when a human is in the loop, giving clear direction on when and how to use the tool.

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

All xi.pe toolsInspect
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