Skip to main content
Glama

Workotron Skills

Mark a listing or a post for the user

mark
Idempotent

Give one of the user's marks. A thumb on a listing: up, down, or none to take it back; a skill is rated only after the user took it, so take it with take first. A helpful mark on a post, a comment on a listing or a post in a thread, which the user's own post never takes. Or, on a question the user asked, the mark on the reply that solved it. A post is named by its number, which its line states on the page's markdown: read the page with read first. It needs the user's key. One mark a call: pass thumb, or helpful with post, or solved with post. Mark only what the user told you to.

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": "mark"
  }
}

Input Schema

NameRequiredDescriptionDefault
postNoThe post's number on the page at address, for a helpful or a solved mark.
thumbNoA listing's thumb: up, down, or none to take it back.
solvedNoOn the user's own question, with post: true marks that reply as the answer. False takes the mark back and needs no post.
addressYesThe listing's or the thread's address, full or as its path.
helpfulNoWith post: true marks the post helpful for the user, false takes the mark back.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare that this is a mutating operation (readOnlyHint=false), that it is idempotent, and that it is non-destructive. The description adds useful context beyond this: it requires the user's key, it imposes a one-mark-per-call limit, it depends on prerequisites being completed first, and marks can be revoked by passing 'none' or false. Those details are valuable, but the definition still does not describe what a successful response looks like beyond what the output schema provides.

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

Conciseness3/5

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

The definition is front-loaded and dense with operational detail, but the sentence structure is idiosyncratic and hard to parse; for example, 'A helpful mark on a post, a comment on a listing or a post in a thread, which the user's own post never takes' is a fragment with ambiguous scope. It covers a lot of ground in about 95 words with little filler, but the readability cost is real.

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?

Given that an output schema exists, an auth requirement, prerequisite sibling calls, mutual exclusivity of parameters, and revocation paths are all covered, the description is nearly complete. The remaining gap is a clear statement of what the 'helpful' and 'solved' modes return or confirm, plus the ambiguity about comments.

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 parameters are documented at the schema level and a sighted agent could call the tool from that alone. The description still adds meaning the schema does not: which parameter combinations form the valid call shapes ('thumb', 'helpful with post', 'solved with post'), and the rule that solved=false takes the mark back with no post. It stops short of clarifying edge cases, such as whether 'helpful' works on comments in the same way as on posts.

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?

Names the specific verb (mark) and enumerates the exact resources it applies to: a listing's thumb, a post's helpful mark, and the solved mark on a reply. An agent can distinguish this from siblings 'take' and 'read', which are explicitly named as prerequisites rather than substitutes.

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

Usage Guidelines5/5

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

Gives explicit when-to-use and when-not guidance: 'a skill is rated only after the user took it, so take it with take first' and 'read the page with read first' establish ordering against named siblings. It also constrains the call shape ('One mark a call: pass thumb, or helpful with post, or solved with post') and adds a consent gate: 'Mark only what the user told you to.'

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