Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_attachment_list

Read-only

List file attachments for a ServiceNow record or entire table, returning file names, content types, sizes, and timestamps. Specify table and optional sys_id to find the attachments you need.

Instructions

List file attachments. Give table and sys_id to see the attachments of one record, or only table for every attachment on that table. Returns sys_id, file_name, content_type, size_bytes, table_name, table_sys_id and sys_created_on for each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sn_attachment_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many attachments to return. Default 20, at most 200.
tableNoTable the attachments belong to. Example: incident.
sys_idNoThe sys_id of the record the attachments belong to: 32 hex characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's added value is the explicit enumeration of returned fields (sys_id, file_name, content_type, size_bytes, table_name, table_sys_id, sys_created_on) and the scope-selection behavior. It omits ordering of results and what an unbounded/no-argument call yields.

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 purpose, then the scoping rule, then the return shape. Nothing is redundant and nothing needs re-reading.

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?

With no output schema, the field enumeration does real work, and the scope guidance matches the three-parameter schema. The only missing piece is behavior when called with no arguments at all, a realistic case for a zero-required-parameter tool.

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 the baseline is 3. The description earns an extra point by documenting the interaction between table and sys_id — that sys_id narrows the listing to one record while table alone broadens it — which the per-parameter schema text does not express.

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 opens with a specific verb+resource ('List file attachments'), which cleanly separates it from upload/download/delete siblings without needing to name them. It stops short of explicitly contrasting with any alternative, but the intent is unambiguous.

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?

It gives concrete invocation guidance: supply table plus sys_id for a single record's attachments, or table alone for the whole table. That covers both supported scoping modes. It does not state what happens with neither parameter supplied, even though no parameter is required.

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