Skip to main content
Glama

Workotron Skills

Share a skill for the user

share

Send a skill the user made to the directory for review, or a new version of a skill they shared. It needs the user's key and the display name they picked. It takes two calls and one upload. Call it first with no arguments: it answers the sharing agreement, the business areas and the products to pick from, and each field's bounds. Show the user the agreement and go on only when the user says yes to it. Then call it with agreement and details: it checks them and answers a one-time address. Send the skill's folder to that address yourself as one zip, with an HTTP PUT, within 15 minutes. The zip holds SKILL.md at its top, or one folder with SKILL.md at that folder's top. Nothing of the files rides in a tool call. The skill is listed only after Workotron reviews and approves it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "share"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsNoWhat the listing says of the skill. The first answer gives each field's bounds and the ids to pick from.
replacesNoThe address of the user's own listed skill this is a new version of. Absent for a new skill.
agreementNoThe id of the sharing agreement the user said yes to, from this tool's first answer. Absent on the first call.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds substantial behavior the agent could not otherwise know: the two-call handshake, the one-time upload address, the 15-minute window, the HTTP PUT requirement, the required zip layout with SKILL.md at the top, and that review approval gates listing. Nothing here contradicts 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loaded: what it does, what it needs, then the exact two-step sequence. Nearly every sentence carries operational weight (upload format, deadline, review gating). It would read better as numbered steps, and a couple of clauses could be tightened, but there is no filler.

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 multi-step tool with a nested object parameter and an out-of-band file upload, the description covers everything an agent needs to invoke it correctly, including what the first call returns and the consent gate. An output schema exists, so not restating return shapes is appropriate.

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 each field, but the description adds the crucial meaning that `details` fields have bounds and enumerated ids supplied by the first answer, and that `agreement` comes from that same first answer and is absent on the initial call. That sequencing context is genuinely beyond 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 opens with a specific verb and resource: send a skill the user made to the directory for review, or a new version of an already-shared skill. It covers both modes of operation (new skill vs. version update via `replaces`) and distinguishes itself from siblings like `post` or `mark` by scoping to skill directory submission.

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?

It gives an explicit two-phase protocol: call first with no arguments to get the agreement and field bounds, then call again with `agreement` and `details`, and only after the user says yes to the agreement. That is unusually clear when-to-call guidance. It does not name alternative tools, but none of the listed siblings appear to overlap, so the gap is minor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources