Keelen

get_legal_exposure_findings

Read a project's legal exposure findings, worst exposure first.

Returns each finding as an OBSERVATION plus the obligation commonly cited
over that pattern, its citation, the date the citation was last checked,
and whether counsel has reviewed the registry entry (`counsel_reviewed`,
false today for every entry). `exposure_order` is an ORDER, never a score:
there is no grade, no percentage, and no overall state in this output.

Read `not_determinable` before you summarise: those are checks that could
not reach a verdict, and leaving them out would turn a partial review into
a clean answer. The `disclaimer_md` field must reach the user.

`limit` defaults to 25 (max 100). `include_all` adds resolved, dismissed,
and out-of-scope rows to the default actionable set. Read-only, no compute,
no rate limit; it works even while the trigger is closed for the project.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`project_id`	Yes
`include_all`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the annotations: it discloses read-only behavior, no compute, no rate limit, and that it works while the trigger is closed. It also clarifies subtle behavioral semantics like exposure_order being an ORDER not a score, the importance of not_determinable findings, and that counsel_reviewed is currently false for every entry.

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 dense but every sentence earns its place: purpose, output semantics, critical caveats, and parameter behavior are each covered without fluff. The most important purpose statement is front-loaded before the detailed caveats.

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?

Given the output schema exists, the description still adds essential context such as the ordering guarantee, the not_determinable caveat, disclaimer handling, and parameter defaults. An agent has everything needed to call this tool correctly and interpret its results safely.

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 description coverage is 0%, but the description compensates well: it explains the effect of include_all (adding resolved, dismissed, and out-of-scope rows) and gives limit's default and maximum. project_id is not described, but its meaning is immediately inferable from the tool name and resource context.

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 starts with a specific verb and resource: 'Read a project's legal exposure findings, worst exposure first.' It clearly distinguishes this from sibling tools by domain (legal exposure) and operation (read vs. run), so an agent can tell it apart without opening the schema.

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

Usage Guidelines4/5

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

The description gives clear context: it is a read-only listing tool, works even while the trigger is closed, and has an include_all mode for broader scope. However, it does not explicitly name alternatives such as run_legal_exposure_review or get_control_gap_findings, so it provides context without explicit exclusions.

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

All Keelen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.