Skip to main content
Glama
Mipiti

Mipiti MCP Server

by Mipiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Reconciliation Candidates

list_reconciliation_candidates

Lists duplicate entity candidates a child model authored that resemble inherited entities; review and resolve each to prevent coverage distortion.

Instructions

Entities a child model authored that look like ones it inherits. Read-only.

Use on a child model in a recursive tree to find duplicates before they distort coverage; decide each with decide_reconciliation_candidate.

  • disposition="active" (default): the open queue, paginated (page, page_size). {model_id, flag_enabled, total, tiers: {certain, heuristic}, page, page_size, candidates: [{kind, own_qid, inherited_qid, tier, reasons}]}. Tier certain is a deterministic match, safe to apply; heuristic is a fuzzy name/description match that needs review. Rejected pairs are left out.

  • disposition="rejected": the pairs recorded as NOT duplicates, oldest first and not paginated: {model_id, flag_enabled, rejections: [{id, model_id, kind, own_qid, inherited_qid, rejected_by, rejected_at}]}. An id is what an unreject names.

Where composition is not available both come back empty with flag_enabled: false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
model_idYes
page_sizeNo
dispositionNoactive
server_versionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.84.0
    • removedInput schema / properties / disposition / description
      Removed value: -"Which side of the queue to read — ``\"active\"``\n(default, open candidates) or ``\"rejected\"`` (persisted\nnot-a-duplicate decisions)."
    • removedInput schema / properties / model_id / description
      Removed value: -"ID of the descendant threat model."
    • removedInput schema / properties / page / description
      Removed value: -"ACTIVE disposition only. 1-indexed page number. Default 1.\nIgnored when ``disposition=\"rejected\"``."
    • removedInput schema / properties / page_size / description
      Removed value: -"ACTIVE disposition only. Items per page. Default 50.\nIgnored when ``disposition=\"rejected\"``."
  2. Changed4 schema fields changedv0.68.2
    • addedInput schema / properties / disposition
      Added value: +{
+  "default": "active",
+  "description": "Which side of the queue to read — ``\"active\"``\n(default, open candidates) or ``\"rejected\"`` (persisted\nnot-a-duplicate decisions).",
+  "type": "string"
+}
    • changedInput schema / properties / model_id / description
      Previous value: -"ID of the threat model."New value: +"ID of the descendant threat model."
    • changedInput schema / properties / page / description
      Previous value: -"1-indexed page number. Default 1."New value: +"ACTIVE disposition only. 1-indexed page number. Default 1.\nIgnored when ``disposition=\"rejected\"``."
    • changedInput schema / properties / page_size / description
      Previous value: -"Items per page. Default 50."New value: +"ACTIVE disposition only. Items per page. Default 50.\nIgnored when ``disposition=\"rejected\"``."
  3. Addedv0.62.2
  4. Removedv0.62.1
  5. First observedv0.57.0

TDQS

A4.6/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 well: it declares read-only, describes the full return shapes for both dispositions, explains the 'certain' vs 'heuristic' tier semantics and that certain is safe to apply, notes rejections are excluded, and discloses the composition-unavailable edge case returning empty with flag_enabled: false.

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?

Front-loads the purpose and read-only hint, then uses bullets for each disposition with inline response shapes. Dense but every clause adds selection or behavioral information; slightly heavy given how much overlaps the output schema.

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 5-parameter read tool with an output schema, the description covers trigger conditions, both modes, tier meanings, the reject/unreject flow, and the degraded empty-result case. Nothing needed to call it correctly is missing.

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 0%, so the description must compensate. It explains disposition values and the pagination contrast (active paginated via page/page_size, rejected not paginated), but model_id and server_version are never described and page/page_size semantics remain thin. Partial compensation only.

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 ('list reconciliation candidates') and defines exactly what they are: entities a child model authored that duplicate ones it inherits. It distinguishes itself from the sibling decide_reconciliation_candidate by naming it as the follow-up action.

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 when: 'on a child model in a recursive tree to find duplicates before they distort coverage.' It also routes the agent to decide_reconciliation_candidate for disposition, and explains which disposition value selects which result set.

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