Skip to main content
Glama
theonlytruebigmac

N-central MCP Server

list_device_tasks

Read-only

Retrieve scheduled tasks for a device, returning task IDs, names, and statuses.

Instructions

Retrieve scheduled tasks for a specific device. Returns task ID, task name, and status. Returns one page by default — set all: true to auto-paginate. Use format: "csv" for spreadsheet-ready output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceIdYesThe device ID
pageNumberNoPage number (starts at 1)
pageSizeNoNumber of items per page (max 200)
selectNoFilter expression (FIQL/RSQL predicate) — despite the "select" name, this filters rows, it does NOT pick fields. Syntax: `field==value`, join predicates with `;` for AND. Example: `soId==50` returns only the SO with that ID. Not all fields are queryable; unsupported ones error with "Field not found: X".
sortByNoField to sort results by
sortOrderNoSort order: ASC, asc, ascending, natural, desc, descending, reverse
allNoAuto-paginate: fetch every page and return the combined list. Ignores pageNumber/pageSize. Use for complete results; omit to return a single page (cheaper, safer for large environments).
formatNoOutput format: "csv" or "json". Default varies by tool — list_* default to json; report_* default to csv.
Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior; description adds useful behavioral details about return fields (ID, name, status) and pagination behavior.

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 concise sentences, front-loaded with purpose, no superfluous content.

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

Completeness5/5

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

No output schema exists but description adequately conveys return fields and key behavioral aspects (pagination, format), making it complete for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters; description adds context for 'all' and 'format' parameters but does not significantly surpass schema documentation.

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

Purpose5/5

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

Description clearly uses verb 'Retrieve' and resource 'scheduled tasks for a specific device', and distinguishes from sibling tools like 'list_scheduled_tasks' by specifying device-specific scope.

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?

Provides explicit guidance on pagination (all: true) and output format (format: csv), but lacks direct comparison to alternative tools or scenarios when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/theonlytruebigmac/n-central-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server