Skip to main content
Glama

Create compliance PM schedule

create_compliance_pm_schedule

Link a PM schedule to a compliance item, so completing the schedule keeps the item compliant. Requires compliance:write scope. Required: compliance_item_id, pm_schedule_id, required_frequency_days. Resolve both ids first with list_compliance_items and list_pm_schedules.

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": {
      "compliance_item_id": "<compliance_item_id>",
      "pm_schedule_id": "<pm_schedule_id>",
      "required_frequency_days": "<required_frequency_days>"
    },
    "name": "create_compliance_pm_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
weightNoRelative weight of this schedule in the item score. Default 1.
pm_schedule_idYesPM schedule ID (required) - resolve via list_pm_schedules
compliance_item_idYesCompliance item ID (required) - resolve via list_compliance_items
required_frequency_daysYesHow often, in days, the schedule must be completed for the item to stay compliant (required), e.g. 365 for annual

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / compliance_item_id / description
      Previous value: -"Compliance item ID (required)"New value: +"Compliance item ID (required) - resolve via list_compliance_items"
    • changedInput schema / properties / pm_schedule_id / description
      Previous value: -"PM schedule ID (required)"New value: +"PM schedule ID (required) - resolve via list_pm_schedules"
  2. Changed5 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / compliance_item_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • addedInput schema / properties / pm_schedule_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • addedInput schema / properties / required_frequency_days / maximum
      Added value: +9007199254740991
  3. Changed5 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / compliance_item_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • removedInput schema / properties / pm_schedule_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • removedInput schema / properties / required_frequency_days / maximum
      Removed value: -9007199254740991
  4. Changed5 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / compliance_item_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • addedInput schema / properties / pm_schedule_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
    • addedInput schema / properties / required_frequency_days / maximum
      Added value: +9007199254740991
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the mutation profile is covered. The description adds valuable information annotations cannot: the required compliance:write scope and the semantic consequence of the link (completing the schedule keeps the item compliant).

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?

Three short sentences: purpose, prerequisite scope, required ids and resolution path. Front-loaded with the effect, nothing wasted.

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

Completeness4/5

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

Covers what an agent needs to invoke it correctly: scope, required ids, and how to obtain them. The only gaps are the optional weight parameter and whether re-linking is allowed (idempotentHint=false). Minor since no output schema exists to explain.

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 coverage is 100% and the schema already repeats the 'resolve via list_*' hints, so the description's parameter restatement is mostly duplicative. The optional 'weight' parameter is not mentioned in the description at all, leaving no added 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?

States a specific verb and resource ('link a PM schedule to a compliance item') and explains the resulting effect on compliance status, distinguishing it from create_compliance_item and create_pm_schedule.

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?

Gives a clear precondition ('Resolve both ids first with list_compliance_items and list_pm_schedules'), which is real routing guidance. It does not mention the alternative of update_compliance_pm_schedule or when a link should be created versus modified, so it stops short of full exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources