Skip to main content
Glama
theonlytruebigmac

N-central MCP Server

list_scheduled_tasks

Read-only

Retrieve scheduled tasks from N-central environment. Use filters, pagination, or auto-paginate for complete results, and export to CSV for analysis.

Instructions

List all scheduled tasks across the N-central environment. Returns one page by default — set all: true to auto-paginate. Use format: "csv" for spreadsheet-ready output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
Behavior5/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 key behavioral details: default pagination behavior and how to auto-paginate or switch output format. No contradictions with annotations.

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 sentences with no fluff. Opens with purpose, then proceeds to pagination and format tips. Every sentence earns its place.

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 list tool with no output schema, the description explains pagination defaults and output options adequately. Could mention default output format (JSON) or sorting, but schema covers those. Annotations supply safety context. Sufficient for effective use.

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 covers all parameters with descriptions (100% coverage). Description enhances understanding of key parameters like 'all' (auto-paginate) and 'format' (spreadsheet-ready), adding value beyond the raw schema.

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 states verb 'list' and resource 'scheduled tasks' with scope 'across the N-central environment'. It is specific and distinguishes from sibling tools like list_devices or list_customers by targeting a unique resource.

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 actionable tips on pagination (default one page, use all:true for full results) and format (use format:csv for spreadsheet output). Does not explicitly state when to use this tool over alternatives, but given it's the only scheduled task list, the context is clear.

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