exim__collection__copy-toCopies a collection with its items, columns and provenance to another existing account as an independent copy. The source is unchanged.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Latest month, YYYY-MM. | |
| name | No | Name for the copy (defaults to source) | |
| collectionId | Yes | Collection name or id |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| stats | No | ||
| _debug | No | ||
| summary | Yes | ||
| warnings | No | ||
| nextActions | Yes | ||
| correlationId | No |
Changes observed during successful MCP inspections.
Input schema / properties / to / descriptionPrevious value: -"Account to hand the copy to (must already exist)"New value: +"Latest month, YYYY-MM."Input schema / properties / to / descriptionPrevious value: -"Latest month, YYYY-MM."New value: +"Account to hand the copy to (must already exist)"Input schema / properties / to / descriptionPrevious value: -"Account to hand the copy to (must already exist)"New value: +"Latest month, YYYY-MM."Input schema / properties / --collectionIdRemoved value: -{
- "description": "Collection name or id",
- "type": "string"
-}Input schema / properties / --nameRemoved value: -{
- "description": "Name for the copy (defaults to source)",
- "type": "string"
-}Input schema / properties / --toRemoved value: -{
- "description": "Account to hand the copy to (must already exist)",
- "pattern": "[^\\t\\n\\v\\f\\r\\x85\\p{Z}]",
- "type": "string"
-}Input schema / properties / collectionIdAdded value: +{
+ "description": "Collection name or id",
+ "maxLength": 8000,
+ "type": "string"
+}Input schema / properties / nameAdded value: +{
+ "description": "Name for the copy (defaults to source)",
+ "maxLength": 120,
+ "type": "string"
+}Input schema / properties / toAdded value: +{
+ "description": "Account to hand the copy to (must already exist)",
+ "maxLength": 8000,
+ "pattern": "[^\\t\\n\\v\\f\\r\\x85\\p{Z}]",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "--collectionId",
- "--to"
-]New value: +[
+ "collectionId",
+ "to"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$defs": {
+ "value0": {
+ "additionalProperties": false,
+ "properties": {
+ "collectionId": {
+ "type": "string"
+ },
+ "items": {
+ "type": "integer"
+ },
+ "name": {
+ "type": "string"
+ },
+ "to": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "collectionId",
+ "items",
+ "name",
+ "to"
+ ],
+ "type": "object"
+ },
+ "value1": {
+ "anyOf": [
+ {
+ "items": {
+ "type": [
+ "null",
+ "boolean",
+ "number",
+ "string",
+ "array",
+ "object"
+ ]
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "value2": {
+ "anyOf": [
+ {
+ "items": {
+ "$ref": "#/$defs/value3"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "value3": {
+ "additionalProperties": false,
+ "properties": {
+ "command": {
+ "type": "string"
+ },
+ "cost": {
+ "type": "string"
+ },
+ "label": {
+ "type": "string"
+ },
+ "rationale": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "command",
+ "cost",
+ "label",
+ "rationale"
+ ],
+ "type": "object"
+ },
+ "value4": {
+ "anyOf": [
+ {
+ "additionalProperties": {
+ "type": "number"
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "value5": {
+ "anyOf": [
+ {
+ "items": {
+ "$ref": "#/$defs/value6"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "value6": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+ },
+ "value7": {
+ "anyOf": [
+ {
+ "additionalProperties": {
+ "type": [
+ "null",
+ "boolean",
+ "number",
+ "string",
+ "array",
+ "object"
+ ]
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "additionalProperties": false,
+ "properties": {
+ "_debug": {
+ "$ref": "#/$defs/value7"
+ },
+ "correlationId": {
+ "type": "string"
+ },
+ "data": {
+ "additionalProperties": false,
+ "properties": {
+ "context": {
+ "type": [
+ "null",
+ "boolean",
+ "number",
+ "string",
+ "array",
+ "object"
+ ]
+ },
+ "cursor": {
+ "type": "string"
+ },
+ "has_more": {
+ "type": "boolean"
+ },
+ "items": {
+ "anyOf": [
+ {
+ "items": {
+ "$ref": "#/$defs/value0"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "context",
+ "has_more",
+ "items"
+ ],
+ "type": "object"
+ },
+ "nextActions": {
+ "$ref": "#/$defs/value2"
+ },
+ "stats": {
+ "$ref": "#/$defs/value4"
+ },
+ "summary": {
+ "type": "string"
+ },
+ "warnings": {
+ "$ref": "#/$defs/value5"
+ }
+ },
+ "required": [
+ "data",
+ "nextActions",
+ "summary"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly=false, destructive=false, idempotent=false; the description adds real context beyond them by stating the copy is *independent* (later edits don't propagate) and that 'the source is unchanged'. It does not mention required account permissions or behavior on name collisions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with zero filler, front-loading what is copied and then the non-destructive guarantee. Nothing needs to be trimmed.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a write tool with full annotations and an output schema, the description covers scope, source immutability, and target prerequisites. Minor gaps remain around permission requirements and naming-conflict handling, but these are not blocking for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but the `to` property's schema text ('Latest month, YYYY-MM.') is misleading for a destination-account field; the description's 'another existing account' corrects that misreading. It confirms the name default and adds that the copy target must already exist, though it leaves the accepted identifier form (name vs id) for `to` unstated.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb and resource ('Copies a collection ... as an independent copy') and states what is carried over (items, columns, provenance), which distinguishes it from collection__create and collection__get. It stops short of explicitly naming a sibling to route against, but the scope is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied rather than stated: 'to another existing account' signals the prerequisite of a target account, but there is no explicit when-to-use/when-not guidance or comparison to create/get/list. An agent can infer the scenario but must reason about it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.