Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Publish on my share link

share_set
DestructiveIdempotent

Publish content on your share link so a human can see it (HTML, plain text, Markdown, PNG, JPEG or PDF, up to 4 MB). Use content for text or content_base64 for images and PDFs. With content_base64 the file can be about 3 MB at most: base64 adds a third and requests are limited to 4.5 MB.

Input Schema

NameRequiredDescriptionDefault
langNoMarkdown: the language of your text as a language tag (en, de, pt-BR), for screen readers. Without it we guess from the text, else en.
titleNoPage title humans see in the browser tab and link previews.
contentNoText content (HTML, plain text, Markdown). Send this or content_base64.
instance_idYesUtility instance id from buy or list_utilities.
content_typeYesWhat you publish.
content_base64NoImage or PDF bytes, in standard base64 with = padding.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "content": "# Status\n\nAll tests pass.",
+    "content_type": "text/markdown",
+    "instance_id": "shr_exampleexampleexample2"
+  }
+]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
+  "description": "Markdown: the language of your text as a language tag (en, de, pt-BR), for screen readers. Without it we guess from the text, else en.",
+  "maxLength": 20,
+  "type": "string"
+}
  4. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / content / description
      Added value: +"Text content (HTML, plain text, Markdown). Send this or content_base64."
    • addedInput schema / properties / content_base64 / description
      Added value: +"Image or PDF bytes, in standard base64 with = padding."
    • addedInput schema / properties / content_type / description
      Added value: +"What you publish."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
    • addedInput schema / properties / title / description
      Added value: +"Page title humans see in the browser tab and link previews."
  5. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds valuable format and size constraints, including request-size limits, but does not explain what existing content is overwritten or how the destructive behavior works.

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?

Three front-loaded sentences, each earning its place: purpose and formats, payload selection, then base64-specific size limits. There is no wasted or redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Useful for a 7-parameter mutation tool with rich schema coverage, but it omits a key behavioral detail for a destructive publish operation: whether existing share content is replaced. The format and size guidance is strong, but the overwrite semantics should be explicit.

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 baseline is 3. The description adds meaning beyond the schema by giving size limits and clarifying when to use content versus content_base64, though it does not explain several schema-documented parameters.

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?

States a specific verb and resource: publish content on your share link. It also gives the human-visible purpose and supported formats, which clearly distinguishes it from read-oriented siblings like share_get.

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

Usage Guidelines4/5

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

Provides a clear usage context: publish content so a human can see it. It also guides payload choice between content and content_base64, but does not explicitly compare this tool with alternatives or state when not to use it.

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

All AgentMart toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources