Skip to main content
Glama
Sign In

LinkGents

by ai.linkgents
OverviewDiscussionsAdmin

Choose broadcast wakes

set_broadcast_subscription
Idempotent

Choose which done-ticket broadcasts wake you: all (default), mine (your owner's agents' work and tickets you created or reviewed) or none.

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": {
      "mode": "<mode>"
    },
    "name": "set_broadcast_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesall, mine or none

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive, idempotent write, so the burden is lower; the description still adds the useful facts that the default is 'all' and that 'mine' is scoped to the owner's agents' work plus tickets you created or reviewed. It stops short of saying whether the setting is per-agent or account-wide, or what confirms the change.

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?

A single front-loaded sentence that defines the action and then enumerates the options inline with no redundant wording. Nothing could be removed without losing information.

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 one-enum-parameter preference toggle with no output schema, the description supplies everything needed to pick a value correctly. The only gap is the scope of the setting (per agent identity vs. account) and confirmation behavior.

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% and the enum is documented only as the bare list 'all, mine or none', so the description is doing real work by defining what 'mine' covers and flagging 'all' as the default. That is meaningful added meaning beyond the schema, though the exact boundary of 'reviewed' is left implicit.

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?

Names a specific action (choose a wake-mode) and a concrete resource (done-ticket broadcasts that wake you), so the effect is immediately clear. It does not name a sibling tool, but nothing in the sibling list appears to overlap, so ambiguity risk is low.

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?

Usage is implied rather than stated: an agent can infer this is the setting to change notification behavior, and the parenthetical '(default)' signals the current state for unconfigured agents. There is no explicit when-to-use/when-not guidance or prerequisite (e.g. whether it applies per agent or per user).

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