AbleSign MCP

get_folder

Retrieve a media folder by its ID to access or view the folder details in the AbleSign digital signage system.

Instructions

Get a media folder.

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": {
      "folder_id": "<folder_id>"
    },
    "name": "get_folder"
  }
}

Input Schema

Name	Required	Description	Default
`folder_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

C2.4/5.0

Behavior1/5

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

No annotations are present, so the description must fully convey behavioral traits. However, it simply says 'Get a media folder' with no disclosure of idempotency, side effects, error handling (e.g., if folder_id is invalid), or authentication needs. The description is insufficient for an agent to understand the tool's behavior.

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?

The description is extremely concise at 4 words, with no extraneous content. However, it is terse to the point of under-specification. Every word is necessary, but more detail would be beneficial, making it barely adequate for a tool with one parameter.

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?

The tool has an output schema (not shown) but the description does not mention return values, error cases, or example usage. Combined with a simple parameter set, the description lacks completeness for an agent to reliably use the tool without additional context.

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?

The input schema has one parameter 'folder_id' with an integer type but no description. The tool description does not explain what 'folder_id' represents (e.g., the unique identifier) or any constraints (e.g., must exist). With 0% schema description coverage, the description provides no supplementary meaning beyond the parameter name.

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 'Get a media folder' specifies a clear verb ('Get') and resource ('media folder'), matching the tool name. However, it lacks differentiation from sibling tools like 'list_folders' (which lists folders) or 'get_media_file' (which gets a file). The purpose is clear but minimal, not achieving full distinctiveness.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or when not to use it. For example, it does not clarify that this tool retrieves a single folder by ID, while 'list_folders' retrieves multiple folders.

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

Deploy Server