Smartschool MCP Server

get_attachments

Retrieve a list of attachments for a given message ID, including file names, sizes, and IDs for downloading.

Instructions

List all attachments for a specific message.

Args: message_id: The ID of the message to get attachments for (from get_messages results).

Returns: Dictionary with attachment list including file names, sizes, and IDs for downloading.

Examples: - get_attachments(249184) -> List attachments for message 249184

Input Schema

TableJSON Schema

Name	Required	Description	Default
`message_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Sep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_attachmentsDictOutput",
+  "type": "object"
+}

First observedv0.2.0Jun 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does disclose the return shape: a dictionary with file names, sizes, and IDs for downloading. It also implies a read-only listing operation. It stops short of covering edge cases or authentication, but it is still reasonably transparent for a simple list tool.

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?

The description is front-loaded with a clear one-sentence purpose, followed by compact Args, Returns, and Examples sections. Every part adds value, and the example makes the usage immediately concrete without any filler.

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 single-parameter tool with an output schema, the description covers the input source, returned data, and the downstream use of the IDs for downloading. Minor omissions like empty-result behavior or auth requirements are not critical here, but the description also does not explicitly route the agent to download_attachment.

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 description coverage is 0%, and the description compensates well by explaining message_id as 'The ID of the message to get attachments for' and specifying it comes from get_messages results. The example reinforces the expected integer format, adding meaning beyond the bare schema type.

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 and resource: 'List all attachments for a specific message.' This clearly identifies the operation and scope, though it does not explicitly differentiate from the sibling tool download_attachment.

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?

It gives a useful context cue by saying message_id comes 'from get_messages results,' which implies when this tool is relevant. However, it does not explicitly explain when not to use it or when to prefer download_attachment instead, leaving the decision partly to inference.

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

Deploy Server