Skip to main content
Glama
ctslone

CData Arc MCP Server

by ctslone

update_report

Update an existing CData Arc report to change its metrics, filters, schedule, or email delivery. Define columns like TransactionsSent or TotalProcessingTime to get the exact data you need.

Instructions

Update an existing Arc report 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
nameYesName of the report to update
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. It only states that it updates an existing configuration, but does not disclose side effects like overwriting, permission requirements, or whether the operation is reversible. The emphasis on Columns is more about parameter usage than behavioral traits.

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?

The description is two sentences and front-loaded with the main purpose. The second sentence, while slightly redundant with the schema, reinforces a critical parameter and does not waste space. Overall concise.

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?

This is a mutation tool with 16 parameters, no annotations, and no output schema. The description is thin, providing no information about return values, side effects, or how the parameters should be combined for different use cases. It only highlights the Columns parameter, leaving much of the tool's behavior unexplained.

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%, so the schema already documents all 16 parameters. The description adds emphasis on the Columns parameter, but the schema's own description for columns already labels it as CRITICAL and lists example values. Thus the description adds no significant meaning beyond the 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?

The description clearly states the tool updates an existing Arc report configuration, using a specific verb and resource. This distinguishes it from sibling tools like create_report and delete_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for updating an existing report, but it does not explicitly say when to use it versus create_report or other alternatives. No exclusions or alternative tools are mentioned.

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