Skip to main content
Glama
Sign In

Oh My Share

by com.openanthropic
OverviewDiscussionsAdmin

upload

Upload one HTML/code payload and get a public share URL plus an edit token. Each call creates a new asset unless idempotencyKey is reused. Anonymous uploads are rate-limited to 10/hour and 50/day per IP; authenticated uploads are limited per account. Content is public unless password-protected and expires after expiresIn (default 7d). Use upload_site for multi-file sites, view to read back, list_assets for your own files, or delete to remove one.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoOptional comma-separated tags.
titleNoOptional title shown in the viewer and gallery metadata.
contentYesHTML or code to publish (required, max 500 KB).
filenameNoOptional display filename used in the title and download name (max 200 chars).
languageNoContent language hint, e.g. html, css, js, json, markdown. Default html.html
passwordNoOptional password; the web view asks for it before showing content.
expiresInNoRetention: 1h, 24h, 7d, 30d, 90d, or 0 for permanent. Default 7d.7d
descriptionNoOptional description for the asset.
idempotencyKeyNoOptional 1-128 char retry key. Reusing it with the same payload returns the original asset; the edit token is only returned to the original caller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description adds substantial context beyond the annotations: each call creates a new asset unless idempotencyKey is reused, anonymous uploads are rate-limited to 10/hour and 50/day per IP, authenticated uploads are limited per account, content is public unless password-protected, and assets expire after expiresIn (default 7d). This goes well beyond the safety hints in the annotations.

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 dense but well front-loaded: it starts with what the tool does and what it returns, then adds constraints and sibling routing. Every sentence carries distinct, useful information.

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?

For a mutation tool with no output schema, the description covers the return values (public share URL and edit token), visibility and expiry behavior, rate limits, idempotency semantics, and explicit sibling alternatives. Nothing material is missing for an agent to call it correctly.

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 description coverage is 100%, so the baseline is 3. The description still adds useful meaning about parameters: it explains that expiresIn defaults to 7d, that content is public unless password-protected, and that idempotencyKey re-use returns the original asset with the edit token only for the original caller. These implications exceed the schema text.

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 and resource: 'Upload one HTML/code payload and get a public share URL plus an edit token.' It immediately distinguishes this from sibling tools by naming upload_site, view, list_assets, and delete with their respective roles.

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 explicitly routes the agent: use upload_site for multi-file sites, view to read back, list_assets for your own files, and delete to remove one. When-to-use guidance is clear and alternatives are named with conditions.

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

All Oh My Share toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources