Skip to main content
Glama

Context — ctxt.io

by io.ctxt

Create a ctxt.io share link

create_context

Share text, markdown, code, or HTML as an auto-expiring ctxt.io link. For visual output (styled reports, tables, charts, diagrams) prefer format=html with self-contained HTML: inline CSS and inline SVG render fully; is stripped server-side and JavaScript never runs, so keep it static. Free expiries: 5m, 30m, 1h (default), 8h, 1d — these return the share URL immediately. ttl=30d and the Pro options (name, password) cost $1 one-time: the link is created in a pending state and the result includes a payment_url a human can open in a browser to complete checkout (platforms enrolled for agentic payments receive an acp block instead and can pay programmatically); until payment the link lives 1 day without Pro features. Anyone with the link can read it. The returned delete_token authorizes deletion via delete_context — keep it private.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ttlNoHow long the link stays readable. 5m–1d are free; 30d costs $1.1h
langNoWith format=code: the language to highlight (e.g. python, javascript, diff). Omit to auto-detect.
nameNoPro, ttl=30d only: human-readable name appended to the URL as a slug.
formatNoHow to render the content: text (verbatim), markdown (rendered rich), code (syntax highlighted), or html (sanitized and rendered — best for visual output; inline CSS/SVG work, scripts are stripped).text
contentYesThe content to share (max 4MB).
passwordNoPro, ttl=30d only: password required to read the link. Access control, not encryption — content is plaintext at rest.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
acpNoPresent when this deployment accepts Agentic Commerce Protocol payments: checkout_endpoint + item_id let an enrolled agent platform complete the $1 purchase without a browser.
urlYes
x402NoPresent when this deployment accepts x402 payments: any agent with an x402 wallet can pay the $1 via the upgrade_context tool — no enrollment.
json_urlYes
text_urlYes
expires_atYes
manage_urlYesThe share URL with ?t=<delete_token> already appended: opening it in a browser unlocks delete/upgrade for this link — share it only with the link's owner.
payment_urlNo
delete_tokenYesShort creator token: authorizes delete_context, and appended to the share URL as ?t=<delete_token> it unlocks delete/upgrade in a browser — keep it private.
markdown_urlYes
pending_paymentYes
paid_ttl_secondsNo
current_ttl_secondsYes

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses critical behaviors beyond annotations: script stripping server-side, JavaScript never runs, free TTLs return URL immediately, paid TTL creates pending state with payment_url/acp block, Pro features depend on payment, plaintext at rest for password, and anyone with the link can read it. Annotations include openWorldHint=true, readOnlyHint=false, idempotentHint=false, destructiveHint=false — the description elaborates these with concrete consequences (non-idempotent paid flow, not read-only because it creates resources).

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?

The description is dense and information-rich, front-loading the core purpose and then layering caveats in a logical order (visual output, TTLs, payment flow, security). It loses one point because the later sentences pack several distinct behaviors into long compound sentences, which slightly reduces scanability for an agent.

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?

The description fully covers a complex 6-parameter tool with outputs, payment flows, security caveats, and sibling routing. It even explains the returned delete_token and its relationship to delete_context. With a 100%-coverage schema, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all six parameters. The description adds value by explaining the payment implication for ttl=30d, the stripped-script caveat for format=html, auto-detection for lang, and the plaintext-at-rest caveat for password. It doesn't restate parameter names, but adds behavioral semantics the schema cannot convey.

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 states a specific verb+resource: "Share text, markdown, code, or HTML as an auto-expiring ctxt.io link." This clearly distinguishes the tool from its siblings (delete_context, read_context) by focusing on link creation. The function is unambiguous.

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 gives explicit when-to-use guidance: prefer format=html for visual output, explains free vs paid TTL choices, and notes that delete_token authorizes deletion via delete_context. It also distinguishes the Pro payment flow from immediate link creation. This is rich, actionable routing information.

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

All Context — ctxt.io toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct action on the same resource (ctxt.io links): create, read, and delete are clearly separable with no overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with clear verbs (create, read, delete) and the same noun (context), making the pattern predictable.

Tool Count5/5

Three tools is well-scoped for a simple link-sharing service, covering the essential lifecycle operations without unnecessary extras.

Completeness5/5

The tool surface fully covers the expected lifecycle for shareable links (create, read, delete), with no obvious missing operations for the stated purpose.

Resources