Mipiti MCP Server

by Mipiti

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Judge Objectives

judge_objectives

Queue judgements for threat-model objectives missing control assessments, with credit estimates before confirmation.

Instructions

Have judged every objective whose mitigation group has no judgement for its current controls and none queued (the diagnosis's not_judged, or objectives reading awaiting_judgement). Mutating only with confirm_estimate=True; may consume credits then. Adding or implementing controls does not move such an objective; a judgement does. judging objectives are already queued: wait for them.

Call with confirm_estimate=False (the default): nothing is queued or charged; the answer carries diagnosis, scope, ungrouped and estimate (credits, objectives, computed_at, rate_version). Show the user the estimate.
Once they agree, call with confirm_estimate=True: each objective in scope is queued (confirmed: true, queued), metered at actuals as it runs, and status_detail is the fresh status.

ungrouped objectives have no mitigation group and are never judged: group their controls with set_mitigation_groups first.

A judgement is not a repair: it can come back insufficient or undecided, which counts the objective as uncovered or undecided, work for strengthen_controls. judge_objective does the same for one.

Refusals come back as data, {confirmed: false, queued: 0, http_status, code, message}: 409 control_generation_in_progress (poll get_control_generation_status), 402 insufficient_credits / quota_exceeded (with estimated_credits), 503 (judging unavailable). An unknown id in co_ids is a 400 error.

Input Schema

TableJSON Schema

Name	Required	Description
`co_ids`	No	Optional comma-separated objective IDs; omit for every objective with no judgement and none queued.
`model_id`	Yes	ID of the threat model.
`server_version`	Yes
`confirm_estimate`	No	False (default) estimates; True queues.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.84.0Oct 4, 2026

changedInput schema / properties / co_ids / description

Previous value: -"Optional comma-separated objective IDs to restrict the call\nto. Omit for every objective with no judgement for its current\ncontrols and none queued."New value: +"Optional comma-separated objective IDs; omit for every\nobjective with no judgement and none queued."

changedInput schema / properties / confirm_estimate / description

Previous value: -"False (default) returns the estimate and queues\nnothing; True queues the judgements."New value: +"False (default) estimates; True queues."

Addedv0.83.1Sep 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that the tool is mutating only under confirm_estimate=True, that this can consume credits metered at actuals, and enumerates refusal payloads (409 control_generation_in_progress, 402 insufficient_credits/quota_exceeded, 503, 400 on unknown co_ids as data rather than exceptions).

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?

Well-structured with a numbered two-step list and grouped refusal codes, but the opening sentence is dense and awkwardly parsed, and the whole block is longer than strictly needed given the output schema exists. Every section is useful, so little is wasted.

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?

For a mutating, credit-consuming batch tool with an output schema, the description covers the decision procedure, the grouping prerequisite, the sibling alternative, outcome semantics (uncovered/undecided), and full refusal handling. Nothing an agent needs to invoke it correctly is missing.

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 75% and the schema already documents co_ids ('omit for every objective with no judgement') and confirm_estimate. The description reinforces these and adds the meaning of the estimate response subfields (credits, objectives, computed_at, rate_version), going somewhat 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 (have judged), resource (objectives) and a precise scope (those with no judgement and none queued), and explicitly distinguishes itself from the single-objective sibling by noting 'judge_objective does the same for one.' An agent can pick this over judge_objective without opening either schema.

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?

Gives an explicit two-step workflow (call with confirm_estimate=False to estimate, then True once the user agrees), plus when-not conditions: ungrouped objectives must be grouped via set_mitigation_groups first, judging objectives should be waited on, and insufficient/undecided outcomes route to strengthen_controls.

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

Deploy Server