Threpoly

Get detailed per-target and per-agent-cluster results for one heartbeat run belonging to the authenticated Threpoly user's company. Use this after threpoly_list_heartbeat_runs, threpoly_list_failed_heartbeat_runs or threpoly_get_heartbeat_overview when the user asks for technical detail about a specific monitoring cycle. Do not ask the user for a run ID when it can be resolved from a previous Threpoly response. This tool is read-only.

threpoly_get_heartbeat_run

Get details for one detected heartbeat performance change belonging to the authenticated Threpoly user's company. Use this after threpoly_list_heartbeat_performance_changes when the user wants more detail about a specific MICRO or MACRO change, including the affected application, region, target, measured value, historical comparison value or deviation. Do not ask the user for a detection ID when it can be resolved from a previous Threpoly response. This tool is read-only.

threpoly_get_heartbeat_performance_change

Get detailed configuration for one outbound-heartbeat monitor belonging to the authenticated Threpoly user's company. Use this after threpoly_list_outbound_heartbeat_monitors when the user asks for a monitor's expected interval, protocol routes, filename masks, folder mappings, usernames, minimum file sizes, last-seen timestamps or AS2 trading-partner mapping. Do not ask the user for a heartbeat ID when it can be resolved from a previous monitor list. This tool intentionally excludes passwords, password hashes, certificate IDs, secret IDs, private keys and raw certificate material. This tool is read-only.

threpoly_get_outbound_heartbeat_monitor

Get finalized historical heartbeat SLA and uptime metrics for one monitored application belonging to the authenticated Threpoly user's company. Use this tool for questions about SLA, uptime percentage, historical availability, service reliability or availability over a requested date range. The default period is the last 7 days. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. For the latest live health position rather than historical availability, use threpoly_get_heartbeat_overview instead. Clearly state the time period used when presenting SLA values. This tool is read-only.

threpoly_get_heartbeat_sla

Get historical heartbeat timing averages for one monitored application, grouped by weekday, hour range, time block, agent cluster and target. Use this tool for questions about expected performance, typical response times, timing baselines, slow periods, weekday comparisons or regional performance differences. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. For live status, use threpoly_get_heartbeat_overview instead. For detected deviations from established performance, use threpoly_list_heartbeat_performance_changes instead. This tool is read-only.

threpoly_get_heartbeat_averages

Get configuration and safe summary details for one monitored application belonging to the authenticated Threpoly user's company. Use threpoly_list_applications first when the user provides an application name rather than an application_id. Use this tool for questions about the application's configuration or metadata. For a live health summary, use threpoly_get_heartbeat_overview instead. This tool is read-only.

threpoly_get_application

Get details for one configured upload or download company test belonging to the authenticated Threpoly user's company. Use this after threpoly_list_company_tests when the user wants more detail about a specific file-transfer workflow test, such as its application, test type, configuration, schedule, active state or transfer steps. Do not ask the user for a test ID when it can be resolved from threpoly_list_company_tests. This tool is read-only.

threpoly_get_company_test

Get one virtual trading partner folder and the safe details of user accounts assigned to it. Use this after threpoly_list_outbound_folders when the user asks who can access a particular folder. Do not ask the user for a folder ID when it can be resolved from a previous folder list. This tool does not list uploaded files, passwords, physical storage keys or folder nodes. This tool is read-only.

threpoly_get_outbound_folder

List safe AS2 virtual trading-partner configurations belonging to the authenticated Threpoly user's company. Use this tool when the user asks which AS2 trading partners are configured, which applications have AS2 partner mappings, or which remote and local AS2 IDs are in use. Optionally filter by application_id. Use threpoly_list_applications first when the user provides an application name rather than an application_id. Inactive partners are excluded unless include_inactive is true. This tool intentionally excludes certificates, certificate IDs, private keys, secret IDs and internal cryptographic policy. This tool is read-only.

threpoly_list_outbound_as2_partners

List the active monitored targets for one application belonging to the authenticated Threpoly user's company. Targets represent the configured monitored services or server connections, such as SFTP, FTPS, HTTPS or AS2. Use this tool when the user asks which services are monitored for an application, when a target_id is needed for another Threpoly tool, or when a request should be restricted to a specific protocol such as SFTP. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. Do not ask the user for a target ID when it can be resolved with this tool. This tool is read-only.

threpoly_list_targets

List hourly capacity-test performance aggregates for one capacity-test configuration belonging to the authenticated Threpoly user's company. Use this for trend and baseline questions involving capacity-test pass rates, file return quality, average or 95th-percentile round-trip duration, or average send, wait and validation phase durations. The default period is the last 30 days. Use run history for individual-run detail. This tool is read-only.

threpoly_list_capacity_test_performance

List recent runs for one capacity-test configuration belonging to the authenticated Threpoly user's company. Use this for historical questions about pass, warning, failure, timeout or cancellation outcomes; matched, mismatched or missing files; round-trip timing; phase timing; or completion-threshold compliance. The default period is the last 30 days. Use threpoly_list_capacity_tests first to resolve capacity_config_id. This tool is read-only.

threpoly_list_capacity_test_runs

List configured bulk-file capacity tests belonging to the authenticated Threpoly user's company. Use this tool to discover capacity_config_id values and answer which applications, targets and agent clusters have capacity testing configured, whether tests are enabled, their schedules, workloads and completion thresholds. Optionally filter by application_id. Use next_after_id as after_id when another page is available. This tool is read-only.

threpoly_list_capacity_tests

List heartbeat outages that are currently ongoing across the authenticated Threpoly user's company. Use this tool for questions such as whether anything is currently down, whether there are any active incidents, or whether any monitored application has an ongoing outage. For historical incidents that have already ended, use threpoly_list_heartbeat_outages instead. For more detail about one returned outage, use threpoly_get_heartbeat_outage. This tool is read-only.

threpoly_list_ongoing_heartbeat_outages

List the security recommendations associated with the latest security assessment for one monitored application belonging to the authenticated Threpoly user's company. Use this tool when the user asks which security improvements should be made, which cryptographic settings should be changed first, what the highest-priority recommendations are, or whether any recommendations of a particular severity exist. Recommendations may apply to the overall application or to an individual monitored target. Use threpoly_list_applications first when the user provides an application name rather than an application_id. Use the optional severity filter only when the user asks for a specific severity. Describe these as recommendations associated with the latest assessment, not as permanently unresolved issues, because this tool does not track a separate remediation workflow. This tool is read-only.

threpoly_list_security_recommendations

List currently ongoing outbound-heartbeat outages across the authenticated Threpoly user's company. Use this tool first when the user asks whether any expected files or AS2 messages are currently overdue, late or missing, whether a trading partner is late sending a file, or whether there are any active expected-file incidents. Optionally filter by application_id. Use threpoly_list_applications first when the user names an application. An outage remains ongoing until a later matching file or AS2 message closes the incident. This tool is read-only.

threpoly_list_ongoing_outbound_heartbeat_outages

List detected heartbeat performance changes for the authenticated Threpoly user's company. Use this tool when the user asks whether response times have changed, whether any service has become slower or faster, whether there are recent performance anomalies, or whether Threpoly detected a change from an established baseline. Optionally filter by application, heartbeat configuration, MICRO or MACRO change type, and date range. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. For historical timing baselines rather than detected deviations, use threpoly_get_heartbeat_averages. For more detail about one returned detection, use threpoly_get_heartbeat_performance_change. This tool is read-only.

threpoly_list_heartbeat_performance_changes

List security-score assessments where Threpoly detected configuration differences for one monitored application belonging to the authenticated user's company. Use this tool when the user asks whether security settings changed, whether cryptographic configuration changed, whether a score changed recently, or wants a recent security-change history. The default period is the last 30 days. Use threpoly_list_applications first when the user provides an application name rather than an application_id. Set include_details to true when the user requests detailed per-target findings. This tool is read-only.

threpoly_list_security_score_changes

List outbound-heartbeat monitors belonging to the authenticated Threpoly user's company. Outbound heartbeats monitor whether an expected file or AS2 message arrives through a Threpoly virtual trading partner route at an agreed interval. Use this tool when the user asks which expected-file monitors are configured, how frequently files are expected, or which applications have outbound-heartbeat monitoring. Optionally filter by application_id. Use threpoly_list_applications first when the user provides an application name rather than an application_id. Inactive monitors are excluded unless include_inactive is true. This tool returns configuration only. For current late-file incidents or historical outages, use the outbound-heartbeat status and outage tools when available. This tool is read-only.

threpoly_list_outbound_heartbeat_monitors

List ended heartbeat outages belonging to the authenticated Threpoly user's company. Use this tool for historical outage, incident-history, downtime-history or previous-availability-issue questions. Optionally filter by application_id. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. For incidents that are happening now, use threpoly_list_ongoing_heartbeat_outages instead. For more detail about one returned outage, use threpoly_get_heartbeat_outage. This tool is read-only.

threpoly_list_heartbeat_outages

List historical outbound-heartbeat outages for one expected-file monitor belonging to the authenticated Threpoly user's company. Use this tool when the user asks whether expected files were late or missing in the past, wants expected-file incident history, or asks how long a previous missing-file outage lasted. Use threpoly_list_outbound_heartbeat_monitors first when the user provides an application name or describes a monitor without a heartbeat_id. For currently overdue expected files, use threpoly_list_ongoing_outbound_heartbeat_outages instead. This tool is read-only.

threpoly_list_outbound_heartbeat_outages

List the monitored applications belonging to the authenticated Threpoly user's company. Use this tool first when the user refers to an application by name, asks which applications are monitored, or needs an application_id for another Threpoly tool. Match application names case-insensitively. Do not ask the user for an application ID when it can be resolved with this tool. This tool is read-only.

threpoly_list_applications

List lightweight heartbeat run summaries for one monitored application belonging to the authenticated Threpoly user's company. Use this tool when the user asks to review recent monitoring checks, heartbeat history or recent runs for an application. The default period is the last 24 hours. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. For failed runs only, use threpoly_list_failed_heartbeat_runs instead. For details about one returned run, use threpoly_get_heartbeat_run. This tool is read-only.

threpoly_list_heartbeat_runs

List recent security-score assessments for one monitored application belonging to the authenticated Threpoly user's company. Use this tool when the user asks how an application's security posture has evolved, whether its score has changed, or wants recent assessment history. Use threpoly_list_applications first when the user provides an application name rather than an application_id. Set unique to true when the user wants significant score change points rather than every assessment. This tool is read-only.

threpoly_list_recent_security_scores

List recent outbound-heartbeat validation results for one expected-file monitor belonging to the authenticated Threpoly user's company. Use this tool when the user asks whether expected files or AS2 messages arrived, whether the latest check passed, when matching files were last received, or wants recent expected-file validation history. The default period is the last 24 hours. Use threpoly_list_outbound_heartbeat_monitors first when the user provides an application name or describes a monitor without a heartbeat_id. Do not describe a MISS result as a confirmed current outage unless the ongoing-outage tool also shows an open incident. This tool is read-only.

threpoly_list_recent_outbound_heartbeat_results

List lightweight summaries for heartbeat runs containing one or more failed checks for one monitored application belonging to the authenticated Threpoly user's company. Use this tool when the user asks about recent failed checks, failed heartbeat runs, connectivity issues, monitoring errors or recent service-specific failures. The default period is the last 7 days. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. Use threpoly_get_heartbeat_run only when more technical detail about one returned run is required. Do not describe failed runs as a confirmed outage unless outage data supports that conclusion. This tool is read-only.

threpoly_list_failed_heartbeat_runs

List upload and download company-test failure events belonging to the authenticated Threpoly user's company. Use this tool when the user asks whether monitored file-transfer workflows have failed, whether uploads or downloads encountered errors, or whether there were recent end-to-end transfer-test failures. Optionally filter by application, company-test ID and date range. The default period is the last 30 days. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. When the user names a configured workflow test rather than a test_id, use threpoly_list_company_tests first to resolve the ID. Do not confuse company-test failures with heartbeat connectivity failures or heartbeat outages. This tool is read-only.

threpoly_list_company_test_failures

List configured upload and download company tests belonging to the authenticated Threpoly user's company. Company tests monitor file-transfer workflows and are separate from heartbeat connectivity checks. Use this tool when the user asks which upload tests, download tests, file-transfer workflow tests or end-to-end transfer checks are configured. Optionally filter by application_id. When the user provides an application name rather than an application_id, use threpoly_list_applications first to resolve the ID. For details about one returned workflow test, use threpoly_get_company_test. For failure events, use threpoly_list_company_test_failures. This tool is read-only.

threpoly_list_company_tests

List active customer-facing Threpoly virtual trading partner endpoints for ad-hoc file transfer over SFTP, FTPS, HTTPS and AS2. Use this tool when the user asks how to connect to Threpoly for file transfer, which protocols can be used, which hostname should be used, or which ports are available. For AS2, the response includes the submission URL and safe server-level AS2 requirements. AS2 trading-partner-specific settings are handled separately and are not returned by this tool. This tool intentionally excludes passwords, secrets, certificates, host-key configuration and internal cryptographic policy. This tool is read-only.

threpoly_list_outbound_transfer_endpoints

List virtual trading partner folders belonging to the authenticated Threpoly user's company. Use this tool when the user asks which folders are available for file transfers to Threpoly or wants to know how many user accounts are assigned to each folder. These folders apply to SFTP, FTPS and HTTPS folder-based transfers. AS2 uses trading-partner configuration with an inbound folder mapping instead. Optionally filter by application_id. Use threpoly_list_applications first when the user provides an application name rather than an application_id. This tool does not list uploaded files, physical storage keys or folder nodes. This tool is read-only.

threpoly_list_outbound_folders

List safe virtual trading partner user details for the authenticated Threpoly user's company. Use this tool when the user asks which accounts can connect to the Threpoly virtual trading partner or which outbound transfer usernames exist. These user accounts apply to SFTP, FTPS and HTTPS folder-based transfers. AS2 uses trading-partner configuration instead. Optionally filter by application_id. Use threpoly_list_applications first when the user provides an application name rather than an application_id. Never ask for, return or describe passwords or password hashes. This tool is read-only.

threpoly_list_outbound_users