Skip to main content
Glama

Coline

Copy a shared file

copy_shared_file

Saves a copy of a file someone shared in a conversation to the person's drive.

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>",
      "type": "<type>",
      "conversationId": "<conversationId>",
      "messageId": "<messageId>",
      "fileId": "<fileId>"
    },
    "name": "copy_shared_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
typeYes
fileIdYes
driveIdNoDefault the person's own drive.
parentIdNo
messageIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdYesChannel or direct message id, from list_conversations.

Output Schema

NameRequiredDescriptionDefault
fileYes
routeYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent operation. The description adds useful context that the source is a conversation-shared file and the target is the user's own drive, but it does not disclose repeat-copy behavior, what happens on name collisions, or whether original sharing permissions carry over — all material for a non-idempotent write.

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 compact sentence with the source and destination front-loaded and no wasted words. It is arguably too short for an 8-parameter mutation, but nothing in it is padding.

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 not be described. Still, for a non-idempotent copy with 8 parameters and low schema coverage, the description omits destination-selection behavior, collision handling, and permission prerequisites, leaving gaps an agent would want covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 38% across 8 parameters, so the description needs to compensate and largely does not. It never explains name, parentId, the type enum, or the driveId defaulting beyond what the schema already says; only the vague notion of 'the person's drive' touches a parameter meaning.

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?

The description states a specific verb ('Saves a copy') and resource ('a file someone shared in a conversation') and scopes the destination ('to the person's drive'). It implicitly distinguishes itself from copy_drive_file by tying the source to a conversation-shared file, though it never names that sibling explicitly.

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 phrase 'someone shared in a conversation' implies the use case (copying an attachment out of a chat) and helps separate it from a generic drive copy. However, there is no explicit when-to-use/when-not guidance, no mention of copy_drive_file as the alternative, and no stated conditions such as permission or ownership requirements.

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