Skip to main content
Glama
Sign In

Lion Reader

by com.lionreader
OverviewDiscussionsAdmin

update_tag

Idempotent

Rename or recolor one of the user's tags (find its ID with list_tags); only the fields you pass change, and the tag keeps its subscriptions. Fails with a not-found error if the tag isn't the user's, or with a name-taken error if another of their tags has the new name (ignoring case). Returns the updated tag.

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": {
      "tagId": "<tagId>"
    },
    "name": "update_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew tag name (max 50 characters, unique per user ignoring case)
colorNoNew hex color (e.g., #ff6b6b). Null to remove color.
tagIdYesTag ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag a non-read-only, idempotent, non-destructive mutation, and the description adds meaningful context beyond them: subscriptions are preserved, unpassed fields are untouched, and two specific failure modes (not-found for non-owned tags, name-taken with case-insensitive comparison) are disclosed. It also states the return value, which the annotations do not cover.

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?

Front-loads the action and scope, then layers prerequisites, mutation semantics, error conditions, and return value in a compact multi-clause sentence with no filler.

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

Completeness5/5

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

For a three-parameter mutation with no output schema, the description covers everything an agent needs: how to get the ID, what changes, what is preserved, how failures manifest, and what comes back.

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%, so lengths, hex pattern, and null-color semantics are already documented. The description still adds real meaning by explaining partial-update behavior (omitted fields are unchanged) and reinforcing case-insensitive name uniqueness at the operation level.

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?

States a specific verb pair and resource ("Rename or recolor one of the user's tags") and immediately scopes it to existing tags by pointing at list_tags for the ID, which cleanly separates it from create_tag, delete_tag, and list_tags.

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 clear preconditions (need a tag ID, obtain it via list_tags) and clarifies that this is a partial update ("only the fields you pass change"), which is the main ambiguity an agent would face. It does not explicitly say when to prefer create_tag or delete_tag instead, so it stops short of full alternatives coverage.

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

All Lion Reader 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