servicenow-api

Get knowledge article attachment

servicenow_get_knowledge_article_attachment

Read-onlyIdempotent

Retrieve a ServiceNow Knowledge Base article attachment using its article Sys ID and attachment Sys ID, returning parsed attachment details for the specified record.

Instructions

Get Knowledge Base article attachment.

:param article_sys_id: The Article Sys ID to search attachments for :type article_sys_id: str :param attachment_sys_id: The Attachment Sys ID :type attachment_sys_id: str

:return: Response containing parsed Pydantic model with information about the retrieved attachment. :rtype: Response

:raises MissingParameterError: If article_sys_id or attachment_sys_id is not provided. :raises ParameterError: If input parameters are invalid.

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": "servicenow_get_knowledge_article_attachment"
  }
}

Input Schema

Name	Required	Description	Default
`textSearch`	No
`sysparm_limit`	No
`sysparm_query`	No
`api_parameters`	No
`article_sys_id`	No
`sysparm_fields`	No
`sysparm_offset`	No
`name_value_pairs`	No
`attachment_sys_id`	No
`sysparm_search_id`	No
`sysparm_search_rank`	No
`sysparm_update_view`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.0Oct 19, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds error behavior (MissingParameterError, ParameterError), which is real value beyond annotations, but it says nothing about pagination, result shape, or why these two Sys IDs are needed together.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Sized appropriately for a docstring, but it is Sphinx boilerplate (:param/:type/:return/:raises) rather than front-loaded prose, and the ':return' line spends words on a parsed Pydantic model that conveys no actionable information.

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

Completeness2/5

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

For a 12-parameter tool with no output schema, the description leaves most parameters undocumented and gives no sense of filtering, pagination, or what the returned attachment contains. It also claims required-parameter errors even though the schema marks nothing required, leaving the required-argument story ambiguous.

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 description coverage is 0% across 12 parameters, so the description carries the full burden, yet it documents only article_sys_id and attachment_sys_id. The ten remaining parameters (textSearch, sysparm_limit, sysparm_query, sysparm_offset, sysparm_fields, name_value_pairs, sysparm_search_id, sysparm_search_rank, sysparm_update_view, api_parameters) are left completely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb+resource ('Get Knowledge Base article attachment'), but it essentially restates the title and adds no differentiation from close siblings such as servicenow_get_attachment or servicenow_get_knowledge_article. An agent can infer the purpose but gets no help distinguishing which attachment-retrieval tool to pick.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternative tools (e.g., get_attachment for non-KB attachments). The reader must infer the calling context entirely from the name.

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

Deploy Server