Skip to main content
Glama
Sign In

FeatureOS

by io.github.featureos
OverviewDiscussionsAdmin

Set changelog labels

set_changelog_labels
Destructive

Set a changelog's labels (tags) to exactly label_ids: adds missing ones, removes extras.

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": {
      "changelog_id": "<changelog_id>",
      "label_ids": "<label_ids>"
    },
    "name": "set_changelog_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
label_idsYesChangelog label (tag) IDs from list_changelog_labels, as a JSON array of integers, e.g. [1779, 1781]. The changelog ends up with exactly these labels; [] clears them.
changelog_idYesThe ID of the changelog.

Output Schema

NameRequiredDescriptionDefault
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description earns its place by explaining exactly what is destroyed: existing labels not in the list are removed. It does not cover atomicity, permissions, or whether the change is reversible, which keeps it from a 5.

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 with no filler; the replace semantics are stated immediately after the resource, which is the highest-value 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?

With two fully documented required parameters, an output schema, and annotations covering the safety profile, the description supplies the one non-obvious behavioral fact (replacement, not append). Minor gaps like permission requirements or error behavior are acceptable given the structured coverage.

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 coverage is 100% and the schema itself already documents the exact-set semantics and the [] clearing behavior. The description's "exactly label_ids" restates rather than extends the schema, so baseline 3 applies.

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 ("Set a changelog's labels") and clarifies the tags synonym, so the resource is unambiguous. The phrase "to exactly label_ids" implicitly separates it from add_tag_to_changelog/remove_tag_from_changelog, but those siblings are never named.

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 replace semantics ("adds missing ones, removes extras") imply when to pick this over the incremental add/remove tools, but no explicit when-to-use or when-not-to-use guidance is given, and no sibling is named as the alternative.

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

All FeatureOS 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