Skip to main content
Glama
Sign In
huly-mcp-selfhost

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

claim_issue

Lease an issue for a set time so parallel agents skip it and avoid duplicate work, with optional force takeover for stale or conflicting claims.

Instructions

Lease an issue so parallel agents skip it

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": {
      "workspace": "<workspace>",
      "identifier": "<identifier>"
    },
    "name": "claim_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoDefault: HULY_AGENT_NAME or claude
forceNoTake over a foreign claim
minutesNoLease length
workspaceYes
identifierYesIssue id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations only supply destructiveHint=false and a title, so the description carries most of the load. "Lease" conveys a time-bound, cooperative lock with effects on other agents, which is real behavioral context beyond the annotations, but the description is silent on conflict/failure behavior and on lease expiry semantics.

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?

A single clause, front-loaded with the verb+resource and no filler. It is efficient but so terse that efficiency comes at the cost of the behavioral detail an agent would need; not a word is wasted, yet little is delivered.

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?

This is a state-mutating coordination tool with five parameters, no output schema, and near-empty annotations. The description omits what a successful claim returns, whether it fails when already leased, and how the lease ends, which are central to using it correctly.

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 description coverage is 80% (only `workspace` lacks documentation), so the schema does the work on agent, force, minutes and identifier. The description adds nothing about parameter meaning; it does not even clarify that `minutes` bounds the lease described in the sentence. Baseline 3 fits.

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

Purpose4/5

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

"Lease an issue" gives a specific verb (lease) and resource (issue), and the trailing clause explains the effect: concurrent agents will skip the issue. It is distinguishable from the sibling release_issue by implication, though the term "lease" itself is jargon the agent must interpret.

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 phrase "so parallel agents skip it" implies the usage context: coordinating multiple concurrent agents working a queue of issues. There is no explicit when-not guidance, no mention of when the lease should be released or what happens if the issue is already claimed (the `force` parameter in the schema is the only hint).

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