Skip to main content
Glama

Coline

Set up a tag

save_tag
Idempotent

Creates a workspace tag or changes its category, color, description or icon, or archives 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>",
      "name": "<name>"
    },
    "name": "save_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNo
nameYes
colorNo
archivedNo
categoryNo
sortOrderNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNo

Output Schema

NameRequiredDescriptionDefault
tagYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true and destructive=false, so the safety profile is covered and the description does not contradict it – archiving is presented as a non-destructive flag change. The description does add that archiving is reachable through this tool, but it omits the create-vs-update decision rule (name-keyed upsert?), what happens to fields not supplied, and any permission requirements.

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 front-loaded sentence that enumerates the mutable fields without padding. The trailing "or archives it" is slightly tacked on but still earns its place by revealing a mode not visible from the field list alone.

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

Completeness3/5

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

An output schema exists so return values need no explanation, but for an 8-parameter mutation tool at 13% schema coverage the description leaves the upsert key, the handling of omitted or null fields, and sortOrder unexplained. It is adequate to recognize the tool but not fully sufficient to call it correctly.

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 description coverage is only 13%, so the description carries real weight, and it names five of the eight parameters (category, color, description, icon, archived) with their purpose. It still says nothing about name/workspace acting as the identity key or about sortOrder, and does not explain the null-to-clear semantics implied by the anyOf types.

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 specific verbs and resource: "Creates a workspace tag or changes its category, color, description or icon, or archives it." An agent knows it is a create/update/archive operation on tags. It does not differentiate itself from siblings such as tag_file or set_file_tags, so the reader must infer the boundary.

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 only implied by the verb list: use it when you need a tag to exist or to change its attributes. There is no explicit when-to-use versus tag_file/set_file_tags, no prerequisites (e.g. workspace membership), and no statement of what happens if a tag with that name already exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources