armorcode-mcp

List Scan Schedulers

armorcode_list_scan_schedulers

List scheduled scans for a security tool in ArmorCode platform to manage scan schedules and ensure timely security assessments.

Instructions

Schedulers for a security tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "toolName": "<toolName>"
    },
    "name": "armorcode_list_scan_schedulers"
  }
}

Input Schema

Name	Required	Description	Default
`toolName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 9, 2026

TDQS

D1.8/5.0

Behavior2/5

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

No annotations provided; description does not disclose behavioral traits such as idempotency, read-only nature, or required permissions. Simply saying 'Schedulers for a security tool' adds no useful behavioral context.

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

Conciseness2/5

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

The description is extremely short but lacks substance. It is concise yet fails to convey necessary information, making it under-specified rather than efficiently communicated.

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

Completeness1/5

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

Given the presence of many sibling tools for scheduling, a concrete description of what this tool returns (e.g., list of scheduler IDs, names, schedules) is missing. No output schema, so the agent is left guessing the return structure.

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?

The input schema has a required 'toolName' parameter with no description. Schema coverage is 0%, and the tool description does not explain what 'toolName' means or how to use it. No enums or examples are provided.

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 'Schedulers for a security tool.' is vague; it doesn't specify that the tool lists schedulers. The action verb 'list' is only in the name. A clear purpose would be 'List all scan schedulers for a given tool.'

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 vs. sibling tools like 'armorcode_delete_scan_scheduler' or 'armorcode_execute_scan'. The description does not mention prerequisites or alternatives.

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

Deploy Server