Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_dataflow_get_execution_interval

Read-only

Retrieve Data Flow job execution counts grouped by time interval for a specified date range to support dashboard monitoring and trend analysis.

Instructions

Get job execution count statistics for Data Flow dashboard. Returns execution counts grouped by time interval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateYesEnd of the query range (ISO 8601, e.g. 2025-03-20T23:59:59) (required)
startDateYesStart of the query range (ISO 8601, e.g. 2025-03-19T00:00:00) (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.1
    • addedInput schema / properties / endDate
      Added value: +{
+  "description": "End of the query range (ISO 8601, e.g. 2025-03-20T23:59:59) (required)",
+  "type": "string"
+}
    • removedInput schema / properties / endTime
      Removed value: -{
-  "description": "End time for query range (ISO 8601 format)",
-  "type": "string"
-}
    • addedInput schema / properties / startDate
      Added value: +{
+  "description": "Start of the query range (ISO 8601, e.g. 2025-03-19T00:00:00) (required)",
+  "type": "string"
+}
    • removedInput schema / properties / startTime
      Removed value: -{
-  "description": "Start time for query range (ISO 8601 format, e.g. 2024-01-01T00:00:00Z)",
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[
+  "startDate",
+  "endDate"
+]
  2. First observedv1.10.1

TDQS

B3.2/5.0
Behavior3/5

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

annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds that output is aggregated counts grouped by interval, which is useful but minimal; no pagination, granularity, or timezone behavior is disclosed.

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

Conciseness4/5

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

Two short sentences with the purpose and return shape front-loaded. Minor redundancy between 'execution count statistics' and 'execution counts' but no wasted clauses.

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

Completeness3/5

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

For a simple two-parameter read-only stats query the description is minimally adequate, but with no output schema and several near-identically-named siblings it should say more to help disambiguate and describe the returned structure.

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 description coverage is 100% and both required date parameters are fully documented with ISO 8601 examples, so the schema carries the semantics. The description only reinforces that the range drives interval grouping; it adds no new syntax or constraints.

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?

States a clear verb ('Get') and a specific resource ('job execution count statistics ... grouped by time interval'), which distinguishes it from the many list/get siblings. However, it does not distinguish itself from the very similar ncloud_dataflow_get_execution_times or ncloud_dataflow_get_execution_result, so an agent must open schemas to tell them apart.

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 when-to-use guidance and no mention of the closely-named siblings (get_execution_times, get_execution_result, get_job_executions). The agent is left to infer selection from the name alone.

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

Deploy Server

Other Tools