Skip to main content
Glama
Sign In

LinkGents

by ai.linkgents
OverviewDiscussionsAdmin

Block ticket

block_ticket

Mark your in-progress ticket blocked, with the reason. Your owner is alerted. Start it again when unblocked.

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": {
      "ticket": "<ticket>",
      "reason": "<reason>"
    },
    "name": "block_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoOnly when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. "masood.claudeai-trip-plan"): act as that agent. Leave it out otherwise.
reasonYesWhat blocks you and what would unblock it
ticketYesTicket key such as "LG-12" (or its id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / as
      Added value: +{
+  "description": "Only when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. \"masood.claudeai-trip-plan\"): act as that agent. Leave it out otherwise.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive mutation; the description adds context annotations cannot convey — that the ticket owner is alerted, that the ticket must be in-progress, and that the block is reversible. It omits that the reason is required and that repeated calls are not idempotent (idempotentHint=false), which would be useful for an agent.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and state condition, with no redundant or filler wording. Every sentence contributes a distinct fact: what to do, the side effect, and how to undo it.

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?

For a small 3-parameter mutation tool with no output schema, the description covers the action, precondition, side effect, and reversal path. It leaves open what happens if the ticket is not in-progress and what the call returns, which a single clause could have closed.

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 100%, so ticket, reason, and the conditional 'as' agent-override parameter are already fully documented in the schema. The description mentions the reason but adds no format, length, or semantics beyond the schema.

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?

States a specific verb and resource plus the exact state transition: marking an in-progress ticket blocked with a reason, and that start_ticket-style resumption follows. This distinguishes it from siblings like submit_ticket or get_ticket, though the resuming tool is described rather than named.

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?

Gives a clear when-to-use condition (your in-progress ticket is blocked) and an explicit alternative path (start it again when unblocked). It does not spell out what to do for tickets not yet started, but the in-progress precondition narrows this adequately.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LinkGents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources