Skip to main content
Glama
Mipiti

Mipiti MCP Server

by Mipiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Control Objectives

get_control_objectives

Retrieve a threat model's control objective matrix or a single objective, including mapped controls and deterministic structural reachability verdict for assurance analysis.

Instructions

Get the control objective matrix, or one control objective. Read-only.

Two modes, selected by whether co_id is set:

  • Matrix mode (co_id omitted) — returns the model's COs, each with references to the controls that cover it. By default returns a compact summary (total count only); pass offset/limit to page through full CO records.

  • Single mode (co_id set) — returns that one CO's typed fields, the IDs of any controls that map to it, and the deterministic reachability verdict (the structural derivation that backs any reach claim on the CO). Tombstoned COs (removed: true) are returned with the flag set; the verdict is omitted because reach state is frozen at the removal version. offset/limit are ignored in this mode.

For pass/fail assurance scoring use assess_model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
co_idNoIf set, single mode — return this one control objective (e.g. ``CO3``) with its verdict. If omitted, matrix mode.
limitNoMatrix mode — max to return (0 = summary only, no per-CO records).
offsetNoMatrix mode — skip the first N control objectives.
model_idYesID of the threat model.
server_versionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.68.2
    • addedInput schema / properties / co_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "If set, single mode — return this one control objective\n(e.g. ``CO3``) with its verdict. If omitted, matrix mode."
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max to return (0 = summary only, no per-CO records)."New value: +"Matrix mode — max to return (0 = summary only, no per-CO\nrecords)."
    • changedInput schema / properties / offset / description
      Previous value: -"Skip the first N control objectives."New value: +"Matrix mode — skip the first N control objectives."
  2. Changed2 schema fields changedv0.66.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max to return (0=summary only)."New value: +"Max to return (0 = summary only, no per-CO records)."
    • changedInput schema / properties / offset / description
      Previous value: -"Skip first N."New value: +"Skip the first N control objectives."
  3. Addedv0.62.2
  4. Removedv0.62.1
  5. First observedv0.57.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden, and it does so thoroughly: read-only semantics, mode-dependent return contents, tombstone handling, verdict omission, and ignored parameters are all disclosed. This goes well beyond a minimal 'gets data' phrasing.

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?

The description is well-organized with a short opening summary followed by clear bullet-style mode breakdowns. Every sentence carries useful information, and the critical read-only and mode-selection cues are front-loaded.

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

Completeness5/5

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

The description fully covers the tool's behavioral complexity: mode selection, pagination, summaries vs full records, tombstone behavior, verdict semantics, and a pointer to the correct sibling. An output schema is present, so the description need not restate return values, and an agent has enough information to invoke this tool correctly in either mode.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the schema already documents most parameters. The description adds meaningful context beyond the schema by explaining that co_id selects the mode, that limit=0 means summary-only, and that offset/limit are ignored in single mode.

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?

The description clearly identifies the resource (control objective matrix or a single control objective) and the action (Get), and it explicitly frames the operation as read-only. It also distinguishes itself from the sibling assess_model by routing pass/fail assurance scoring to that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It specifies exactly when to use each mode based on whether co_id is set, describes defaults for matrix mode, and states that offset/limit are ignored in single mode. It also explicitly names assess_model as the alternative for pass/fail assurance scoring.

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