connectsecure-mcp

post_report_builder_update_standard_report_settings

Update standard report settings in ConnectSecure to adjust filters, pagination, and report configuration. Provide new settings in the request payload to modify existing report definitions.

Instructions

Create Report Calls POST /report_builder/update_standard_report_settings. Provide route IDs in path_params, filters and pagination in query, and any required request headers in headers. Provide the request payload in body.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`body`	No
`query`	No
`headers`	No
`path_params`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 14, 2026

TDQS

C2/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It does not disclose side effects (e.g., whether settings are overwritten, whether authentication is required, or the response structure). The description mentions 'Provide the request payload' but remains mostly oblivious to mutation risks.

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

Conciseness3/5

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

It is concise (two sentences) and front-loads the primary action, but it is under-specific rather than efficiently structured. The brevity is not earned because it omits crucial details.

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?

Given the tool's complexity (4 generic parameters, no schema, no annotations, an output schema exists but no detail), the description is grossly incomplete. An agent cannot infer required payload structure, domain constraints, or error semantics.

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

Parameters1/5

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

Schema coverage is 0%, and parameters remain generic opaque objects (path_params, query, headers, body). The description adds no meaning beyond the schema—it says to provide these fields but leaves agents guessing what content goes into each.

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

Purpose2/5

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

The description is largely a generic wrapper echoing the endpoint path and HTTP method, with a vague verb 'Create Report'. It does not specify what 'standard report settings' are, what the update affects, or what constitutes success.

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 guidance on when to use this tool versus sibling tools like get_report_builder_get_standard_report_settings or other report builder operations. The description only lists generic HTTP parameter placements, not domain-specific usage context.

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

Deploy Server