Skip to main content
Glama

Create compliance item

create_compliance_item

Create a new compliance item (regulatory requirement). Requires compliance:write scope.

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": {
      "name": "<name>"
    },
    "name": "create_compliance_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCompliance item name (required)
statusNoStatus
system_idNoAssociated system ID - resolve via list_systems
descriptionNoDescription
regulation_referenceNoRegulation or code reference
compliance_period_monthsNoCompliance period in months

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / system_id / description
      Previous value: -"Associated system ID"New value: +"Associated system ID - resolve via list_systems"
  2. Changed4 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_period_months / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / system_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})$"
  3. Changed4 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_period_months / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / system_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})$"
  4. Changed4 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_period_months / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / system_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})$"
  5. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already disclose readOnly=false, destructive=false, idempotent=false, and openWorld=false, so the safety profile is covered; the description's only added value is the required auth scope. It does not warn that, being non-idempotent, repeat calls may create duplicate items, nor does it describe the response.

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?

Two short sentences, zero filler, purpose front-loaded ahead of the permission constraint. It is lean to the point of being sparse for a six-parameter creation tool, but nothing present is wasteful.

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

Completeness3/5

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

There is no output schema, so the description should say what a successful call returns (e.g., the created item and its ID) and it does not. Combined with no guidance on duplicate handling or how compliance items relate to compliance records, it is adequate but leaves real gaps for a mutation tool.

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% and every property carries its own description (including the pointer to list_systems for system_id), so the schema does the heavy lifting. The description adds no parameter-level meaning, which is the baseline 3 case.

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

Purpose4/5

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

Specific verb+resource ("Create a new compliance item") with a clarifying gloss that it is a regulatory requirement, which genuinely disambiguates the domain object. However, it does not distinguish this from siblings like create_compliance_record or create_compliance_pm_schedule, which an agent must disambiguate against in a very crowded namespace.

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 scope prerequisite ("Requires compliance:write scope") gives a usable precondition, but there is no statement of when to use this versus create_compliance_record or the update/list variants, and no note on what to do if the item already exists.

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