ShortsIntel

Rename a collection

rename_collection

Idempotent

Use when renaming a Collection, by id or current name; its Trackers are untouched. Not for changing its members: add_to_collection or remove_from_collection. Price: Free.

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": {
      "collection": "<collection>",
      "name": "<name>"
    },
    "name": "rename_collection"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The Collection's new name.
`collection`	Yes	The Collection, by id or name (case does not matter).

Output Schema

Name	Required	Description	Default
`collection`	No	A named set of Trackers of one kind.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026
- changedOutput schema / properties / collection / additionalProperties
```
Previous value: -trueNew value: +{}
```
- removedOutput schema / properties / collection / properties
```
Removed value: -{}
```

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "collection": {
+      "additionalProperties": true,
+      "description": "A named set of Trackers of one kind.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the rename leaves associated Trackers unchanged, and the call is free of charge. It does not address collision handling if the new name already exists, which keeps it short of 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?

Three short sentences, front-loaded with the usage condition, followed by the exclusion and then the cost note. Every sentence carries a distinct signal and there is no padding.

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 two-parameter rename operation with full schema coverage, rich annotations, and an output schema, the description covers purpose, alternatives, and side effects. Nothing an agent needs in order to call this correctly is missing.

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 already documents both parameters including case-insensitivity on the collection lookup. The description's "by id or current name" restates the schema rather than extending it, so the baseline of 3 applies.

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 and resource ("renaming a Collection") plus the lookup forms (by id or current name) and the scope boundary ("its Trackers are untouched"). An agent can distinguish it from add_to_collection, remove_from_collection, and delete_collection without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("Use when renaming a Collection") and explicit when-not ("Not for changing its members"), with both alternative tools named. Nothing about tool selection is left to inference.

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

All ShortsIntel tools Inspect

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

Need Help?