Skip to main content
Glama
MarkAC007

mcp-server-scf

by MarkAC007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

scf_update_system

Update an existing system record's details, assessment boundary, and recovery objectives; only supplied fields are changed.

Instructions

Update a system record (write — editor+ role), including its boundary and recovery record. All fields are optional; only provided fields are applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew system name
org_idYesOrganization UUID — obtain from scf_list_organizations
statusNoNew lifecycle status
vendorNoNew legacy free-text vendor name (prefer vendor_id)
categoryNoNew free-text category
in_scopeNoAssessment boundary: true (inside), false (outside), or null to mark it undecided
rpo_hoursNoRecovery point objective in hours (≥ 0); null clears
rto_hoursNoRecovery time objective in hours (≥ 0); null clears
system_idYesSystem UUID to update — obtain from scf_list_systems
vendor_idNoNew structural vendor link (UUID, same org) — obtain from scf_list_vendors
criticalityNoBusiness criticality — one of: low, medium, high, critical; null clears
descriptionNoNew system description
system_typeNoNew system classification — one of: cloud_provider, identity_provider, ticketing, logging, security_tool, code_repository, document_management, endpoint_management, vulnerability_management, email_security, security_awareness, password_manager, communication, hr_system, custom
hosting_locationNoWhere the system runs; null clears
catalog_template_idNoNew system-catalog template ID link — obtain from scf_list_system_catalog
data_classificationNoHighest classification of data held — one of: public, internal, confidential, restricted; null clears

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.7.2
    • addedInput schema / properties / criticality
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "low",
+        "medium",
+        "high",
+        "critical"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Business criticality — one of: low, medium, high, critical; null clears"
+}
    • addedInput schema / properties / data_classification
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "public",
+        "internal",
+        "confidential",
+        "restricted"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Highest classification of data held — one of: public, internal, confidential, restricted; null clears"
+}
    • addedInput schema / properties / hosting_location
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 255,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Where the system runs; null clears"
+}
    • addedInput schema / properties / in_scope
      Added value: +{
+  "description": "Assessment boundary: true (inside), false (outside), or null to mark it undecided",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • addedInput schema / properties / rpo_hours
      Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Recovery point objective in hours (≥ 0); null clears"
+}
    • addedInput schema / properties / rto_hours
      Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Recovery time objective in hours (≥ 0); null clears"
+}
  2. Changed2 schema fields changedv3.5.0
    • changedInput schema / properties / system_type / description
      Previous value: -"New system classification"New value: +"New system classification — one of: cloud_provider, identity_provider, ticketing, logging, security_tool, code_repository, document_management, endpoint_management, vulnerability_management, email_security, security_awareness, password_manager, communication, hr_system, custom"
    • changedInput schema / properties / system_type / enum
      Previous value: -[
-  "cloud_provider",
-  "identity_provider",
-  "ticketing",
-  "logging",
-  "security_tool",
-  "code_repository",
-  "document_management",
-  "custom"
-]New value: +[
+  "cloud_provider",
+  "identity_provider",
+  "ticketing",
+  "logging",
+  "security_tool",
+  "code_repository",
+  "document_management",
+  "endpoint_management",
+  "vulnerability_management",
+  "email_security",
+  "security_awareness",
+  "password_manager",
+  "communication",
+  "hr_system",
+  "custom"
+]
  3. First observedv1.7.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description's addition of the editor+ authorization requirement and the PATCH-style semantics ('Only provided fields are applied') is real value beyond structured data. It still omits what happens on conflict/invalid IDs and whether omitted fields are ever cleared versus left untouched (the schema's 'null clears' hints at this but the description doesn't reconcile it with 'only provided fields are applied').

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 compact sentences, front-loaded with the verb and resource, and the authorization and partial-update notes are appended without waste. Only mild redundancy in the parenthetical phrasing, nothing that needs cutting.

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?

For a 16-parameter PATCH tool with no output schema, the description covers the two things an agent most needs: it is a write requiring editor+ rights, and it is a partial update. Return behavior is not described, but with no output schema declared that omission is acceptable; identity/ID sourcing is covered by the schema.

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%, so each of the 16 parameters is already documented in the schema (including vendor vs vendor_id preference and null-clears semantics). The description only loosely groups fields as 'boundary' and 'recovery record' and adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource ('Update a system record') and adds scope hints about what parts of the record are touched (boundary, recovery record). It does not explicitly name or differentiate from the sibling scf_create_system or scf_update_system_capability, so it stops short of full sibling differentiation.

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?

Provides one concrete prerequisite — write requires editor+ role — which helps an agent know when it is permitted to call. However, there is no guidance on when to choose this over scf_create_system, scf_update_system_capability, or scf_batch_update_* tools; usage context is only implied by the name.

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

Deploy Server

Other Tools