Skip to main content
Glama
Mipiti
by Mipiti

get_reach_verdicts

Get reachability verdicts for a child threat model in a composed topology, reflecting inherited components and trust boundaries.

Instructions

Per-CO reachability verdicts over the composed effective topology.

Same shape as get_reachability_verdicts, but evaluated against the merged tree: own components and trust boundaries combined with everything inherited, and qualified ids used for cross-model references. Use this when the model is a child on the composition tree and you need reach state that reflects the ancestor topology, not just the local model document.

Return shape::

{
  model_id, flag_enabled,
  verdicts: [
    {co_qid, asset_qid, attacker_qid,
     kind: "reachable"|"unreachable"|"indeterminate",
     reason: <structural label>},
    ...
  ],
  total, page, page_size,
}

When composition is disabled on the backend, verdicts is empty and flag_enabled: false — fall back to get_reachability_verdicts for the per-model derivation.

Omitting page / page_size defaults to page=1, page_size=100 — the response is paginated and no longer returns every verdict in a single call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-indexed page number (default ``1``).
model_idYesID of the threat model.
page_sizeNoverdicts per page (default ``100``).
kind_filterNorestrict verdicts to one kind — one of ``"reachable" | "unreachable" | "indeterminate"``. Named ``kind_filter`` (not ``kind``) to disambiguate from the verdict object's own ``kind`` field. When omitted, all verdict kinds are returned.
server_versionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Describes pagination (defaults to page=1, page_size=100), filtering with kind_filter, and outputs empty verdicts when composition disabled. No annotations to contradict.

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?

Detailed but well-structured with purpose, return shape, fallback, and defaults. Could be slightly more concise but effective.

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?

Completely addresses a complex tool: purpose, usage context, return shape, fallback behavior, pagination, filtering. Output schema provided in description reduces need for further detail.

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?

Adds context for kind_filter naming disambiguation and pagination defaults, beyond the schema which already has 80% coverage.

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?

Clearly states it provides per-CO reachability verdicts over the composed effective topology, differentiating from get_reachability_verdicts which operates on the local model.

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?

Explicitly states when to use (child model needing ancestor topology) and provides fallback to get_reachability_verdicts when composition is disabled.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mipiti/mipiti-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server