Skip to main content
Glama
Sign In
Waymark

Waymark

by SerjMihashin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task_claim

Claim a pending task by validating agent assignment, capabilities, and dependencies in a single atomic operation.

Instructions

Atomically claim a pending task after validating assignment, capabilities, and dependencies.

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": {
      "id": "<id>",
      "agent_id": "<agent_id>"
    },
    "name": "task_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It states atomicity and validation but fails to disclose side effects (e.g., task state change, failure behavior, permissions required). The behavioral picture is incomplete.

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 a single, front-loaded sentence that efficiently conveys the core action. However, it could be structured better (e.g., separate parameter details) given the lack of schema descriptions.

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

Completeness2/5

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

With no output schema and a complex operation involving validation and state changes, the description omits crucial context: return values, error conditions, and post-claim state. Sibling tools exist but are not contrasted.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description adds no meaning for the two parameters ('id', 'agent_id'). It does not explain what they represent (e.g., task ID, claimant). This is a major gap.

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 uses a specific verb 'claim' and resource 'pending task', clearly distinguishing it from sibling tools like task_create or task_list. It also adds conditions (validating assignment, capabilities, dependencies), making the purpose unambiguous.

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?

The description implies usage for claiming a pending task but does not explicitly state when to use it vs alternatives (e.g., when not to use, prerequisites). Sibling tool names are provided but no comparative guidance.

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