Skip to main content
Glama
vrijsinghani

ArtifactSmith

by vrijsinghani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

share

Publish a public link to an artifact so anyone can view it. Optionally pin a version or set an expiry.

Instructions

Publish a public link. Anyone with the link can open it.

Permission: share.
Arguments: artifact_id (required), version (optional; passing it pins that version), ttl_days (optional; ignored when AM_SHARE_TTL_DAYS is 0), pin (optional).
Returns: state, url, version, follows ("latest" or "pinned"), expires_at, lifetime, reused.
Omit version to keep serving the latest done version on the same URL.
Example: share(artifact_id="art_example")
unshare revokes it immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pinNoFreeze one version. Optional. True with no version pins the latest done version now. False with no version follows later versions.
versionNoDone version to pin. Optional. Omit it to follow the latest done version. Passing a version freezes that version on its own link.
ttl_daysNoShare lifetime in days. Optional. Defaults to AM_SHARE_TTL_DAYS. Ignored when AM_SHARE_TTL_DAYS is 0 (the link lasts until revoked). Otherwise capped by AM_SHARE_TTL_MAX_DAYS.
artifact_idYesArtifact to publish. Required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it names the required permission, explains TTL behavior and the AM_SHARE_TTL_DAYS=0 exception, describes pin vs follow semantics, and notes immediate revocation via unshare. It does not state idempotency/reuse behavior for repeated calls, though the 'reused' return field hints at it.

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?

Front-loaded purpose, then Permission/Arguments/Returns/Example in a scannable block, and ends with the unshare note. Some argument text restates the schema, but it is compact and the example is useful.

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

Completeness4/5

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

An output schema exists so return details are optional, yet the extra Returns list plus example make the tool callable end-to-end. The main remaining gap is sibling differentiation from 'publish' on a toolset that also has 'edit' and 'create'.

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, but the description adds real meaning on top of it: 'passing it pins that version', 'ignored when AM_SHARE_TTL_DAYS is 0', and the follow-vs-pin contrast for version/pin interaction.

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?

States a concrete verb+resource ('Publish a public link') and immediately defines the effect ('Anyone with the link can open it'), so the agent knows exactly what is produced. It does not, however, distinguish this from the sibling 'publish' tool, which the agent must resolve on its own.

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?

Gives clear operating context: requires the share permission, omit version to follow the latest done version, and 'unshare revokes it immediately', which routes the agent to the sibling for teardown. It stops short of an explicit when-to-use-this-over-publish rule.

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

Deploy Server

Other Tools