Skip to main content
Glama

Workotron Skills

Search the directory

search
Read-onlyIdempotent

Find skills and Workotron workflows by words or by #tags, the best match first, 24 a page. Words match a listing's name, its one line and its texts, a typo forgiven on a longer word. A #tag is a business area (#finance, #marketing) or a product (#claude, #chatgpt). Each result carries the listing's name, its kind, its one line and its address: read the address with read, or install it with take. The result says how many pages the answer has: pass page to read the next. A search of words with no kind also answers the forum's threads that hold every word, each with its address to read.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly skills, or only Workotron workflows. Absent for both.
pageNoWhich page of the answer, from 1. The first when absent.
queryYesWords, #tags or both: `invoice reminders`, `#finance`, `newsletter #marketing`.

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 already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add match behavior, and it does richly: best match first, 24 per page, which fields are matched, typo forgiveness on longer words, what a #tag means, and the exact shape of each result. The page-count disclosure is information an agent needs to paginate correctly and is not inferable from 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?

Purpose, matching rules, result contents, and pagination arrive in that order with essentially no filler. Sentences are dense and occasionally clause-heavy ('Each result carries the listing's name, its kind, its one line and its address'), but nothing is redundant or self-referential.

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 three-parameter, schema-complete, output-schema-backed search tool, the description supplies everything an agent needs: what is searched, how ranking and paging work, every result field, and which sibling to call next. No behavioral gap remains that would cause a misinvocation.

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 beyond it: tags denote business areas or products (#finance, #marketing, #claude, #chatgpt), and omitting kind both widens to both listing types and pulls in forum threads — a consequence the schema's 'Absent for both' does not convey.

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 ('Find skills and Workotron workflows by words or by #tags') plus ranking order and page size. It also distinguishes itself from siblings by naming read and take as the follow-up actions for the addresses it returns.

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 routes the agent explicitly to alternatives: use read to open a result's address, take to install one, and pass page to advance. It also explains the special case where a word-only search with no kind additionally returns forum threads. There is no explicit statement of when *not* to search, which keeps it just short of a 5.

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