Skip to main content
Glama
ctslone

CData Arc MCP Server

by ctslone

create_report

Generate a new Arc report with specified metrics, filters, and schedule to monitor transaction performance.

Instructions

Create a new Arc report with specified configuration. The Columns parameter is critical - include the metrics you want to see in the report (e.g., TransactionsSent, TransactionsReceived, TotalProcessingTime, TransactionsSuccess, TransactionsError).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUnique name for the new report (can be any descriptive name)
typeNoType of report. Valid values: 'Connector', 'EDI'
formatNoReport output format (e.g., 'PDF', 'CSV', 'Excel')
columnsNoCRITICAL: Comma-separated list of metrics to include in the report. Valid values: WorkspaceId, ConnectorId, ConnectorType, TransactionsAll, TransactionsSent, TransactionsReceived, TotalProcessingTime, TotalFileSize, TransactionsSuccess, TransactionsError, TransactionsWarning. Always include relevant columns based on what the user is asking for.
endDateNoSchedule end date in ISO format (only used with schedule parameter). Example: 2025-11-04T00:00:00.000-05:00
filtersNoFilters to apply to the report. Use ConnectorType (e.g., 'AS2', 'SFTP', 'FTP') and/or ConnectorId. Example: 'ConnectorType=AS2' or 'ConnectorType=SFTP,FTP;ConnectorId=SFTP1,SFTP2'
summaryNoSummary statistics to include. Valid values: Total, Average, Minimum, Maximum
scheduleNoCron expression for automated report scheduling. Format: 'minute hour day month dayOfWeek'. Example: '30 15 1 * *' runs on the 1st of each month at 15:30
groupRowsNoComma-separated list of dimensions to group the report by. Valid values: Year, Quarter, Month, Week, WorkspaceId, ConnectorType
startDateNoSchedule start date in ISO format (only used with schedule parameter). Example: 2025-11-04T00:00:00.000-05:00
timePeriodNoTime period for the report. Valid values: 'All', 'LastMonth', 'Last3Months', 'Last6Months', 'Last12Months', 'MonthToDate', 'QuarterToDate', 'YearToDate', 'SinceLastRun', 'Custom' (if using Custom, also set timePeriodStart and timePeriodEnd in format: 2025-11-04T00:00:00.000-05:00)
emailReportNoWhether to send the report via email
emailSubjectNoEmail subject line (only used if emailReport is true)
timePeriodEndNoCustom time period end date in ISO format (only used when timePeriod is 'Custom'). Format: 2025-11-04T00:00:00.000-05:00
emailRecipientsNoComma-separated list of email recipients (only used if emailReport is true)
timePeriodStartNoCustom time period start date in ISO format (only used when timePeriod is 'Custom'). Format: 2025-11-04T00:00:00.000-05:00
Behavior2/5

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

With no annotations, the description carries the full burden, but it only states that a report is created. It does not disclose side effects (e.g., saving, immediate execution, scheduling behavior), whether creation is reversible, or what response/ID to expect. This is a minimal disclosure for a potentially complex operation.

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 two sentences, front-loaded with the main action, and every sentence contributes. It avoids repeating schema details while highlighting the key column parameter.

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?

Although the tool has 16 parameters and no output schema, the rich schema descriptions cover all fields, and the description points to the most critical parameter. However, a brief overview of configuration categories (time period, scheduling, email, filters, grouping) would help an agent understand the tool's full capabilities at a glance.

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%, with detailed descriptions for all 16 parameters. The description adds emphasis on the 'Columns' parameter as critical and gives examples, but those examples are already listed in the schema's valid values, so it adds only marginal value beyond the structured field 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?

The description clearly states 'Create a new Arc report' with a specific verb and resource, distinguishing it from siblings like list_reports, get_report, update_report, and delete_report. Mentioning 'specified configuration' reinforces the tool's creation role.

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?

The description makes obvious the tool is for creating new reports, providing clear context for when to invoke it. It does not explicitly contrast with update_report or other alternatives, but the purpose statement alone gives sufficient guidance for typical 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/ctslone/AdminAPI_MCP'

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