Skip to main content
Glama

copy_attachment

Copies an existing ServiceNow attachment to another record entirely server-side, so file bytes never pass through the tool call. Use it to attach the same document to a KB article or incident.

Instructions

Copy an existing ServiceNow attachment onto another record, entirely server-side (requires WRITE_ENABLED=true). The file bytes never pass through this tool call. Ideal for "attach the same document from this record onto that KB / incident".

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": {
      "attachment_sys_id": "<attachment_sys_id>",
      "target_table": "<target_table>",
      "target_record_sys_id": "<target_record_sys_id>"
    },
    "name": "copy_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_nameNoOptional new file name (defaults to the source name)
target_tableYesTable to copy the attachment to (e.g. "kb_knowledge")
attachment_sys_idYessys_id of the source attachment to copy
target_record_sys_idYessys_id of the target record

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.15.1

TDQS

A3.9/5.0
Behavior3/5

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

Adds real value beyond the annotations by disclosing that the copy is server-side and that file bytes never traverse the tool call, plus the WRITE_ENABLED config prerequisite – none of which is in the annotation block. It does not address duplicate behavior (annotations declare idempotentHint=false, so a second call presumably creates a second attachment) or what the call returns.

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 action and mechanism, then the prerequisite, then the use case. Every sentence carries information and nothing is padded.

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

Completeness4/5

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

For a non-destructive mutation with no output schema and fully documented parameters, the description covers action, prerequisite, and a realistic scenario. The remaining gap is outcome behavior – whether a new attachment id is returned or duplicates are possible – which matters given idempotentHint=false.

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 per the baseline the schema already documents all four parameters; the description adds only the contextual note that the target is 'another record' and gestures at KB/incident tables. It stays at the baseline rather than adding format or validation detail beyond the schema.

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?

Specific verb (copy) plus resource (ServiceNow attachment) plus destination (another record), and the 'server-side, bytes never pass through' clause explains the mechanism. It doesn't explicitly contrast with upload_attachment or read_attachment, so the sibling differentiation is implied rather than stated.

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?

The 'Ideal for "attach the same document from this record onto that KB / incident"' sentence gives a concrete triggering scenario, and the WRITE_ENABLED=true prerequisite sets a gating condition. No explicit when-not-to-use or named alternative (e.g. upload_attachment for new files) is given, which keeps it below a 5.

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

Deploy Server

Other Tools