Skip to main content
Glama

Workotron Skills

Take a skill

take
Idempotent

What you need to install a skill: the address of its zip, the folder the zip holds, and each file's path, address, size and SHA-256. Fetch the zip and unpack it into your skills folder, or fetch each file and write it under the skill's folder. Nothing of the files rides in this result. If you cannot fetch an address, read each file with read at its address. With the user's key the skill counts as the user's own copy, counted once. A Workotron workflow is added in the Workotron app, and take says how.

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": {
      "address": "<address>"
    },
    "name": "take"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe skill's address, full or as its path: `unpaid-invoice-chaser`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare idempotency and non-destructiveness, and the description adds useful context: the result omits file contents, ownership is counted once under the user's key, and a fallback to read exists if fetching fails. These are meaningful behavioral details beyond the structured hints, though the division of labor between tool and agent remains slightly ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is a six-sentence paragraph that mixes purpose, output details, agent instructions, and workflow notes without clear front-loading. Sentences like 'Nothing of the files rides in this result' and 'A Workotron workflow is added in the Workotron app, and take says how' are cryptic and reduce clarity.

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?

For a one-parameter tool with an output schema, the description covers install steps, ownership, and failure fallback. However, it remains ambiguous about whether the tool or the agent performs the fetch and unpack, and 'with the user's key' is not explained.

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

Parameters3/5

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

Schema coverage is 100% and the single address parameter is documented in the schema; the description only restates that it is the address of the zip. It adds no additional meaning, examples, or constraints beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that the tool provides what is needed to install a skill, but it does so indirectly through a fragment list rather than a direct statement of the tool's action. It never explicitly says whether the tool performs installation or returns a manifest, which leaves the core verb-resource relationship somewhat vague.

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

Usage Guidelines3/5

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

It implies use when installing a skill and names a fallback to the sibling read tool when an address cannot be fetched. However, it offers no explicit when-to-use or when-not-to-use guidance relative to other siblings like search or share, leaving the agent to infer the context.

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