Keelen

Get Legal Exposure Findings

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.

`not_determinable` lists the checks that could not reach a verdict;
omitting them 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

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 19, 2026

TDQS

A3.5/5.0

Behavior1/5

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

The description claims the tool is 'Read-only, no compute, no rate limit,' but the annotations declare readOnlyHint=false, directly contradicting that claim on the same axis. Although the description otherwise adds rich behavior (no rate limit, availability while the trigger is closed, the required disclaimer_md disclosure), the explicit contradiction with the annotation forces a 1.

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 one-line purpose before explaining return shape, ordering caveats, and parameters. It is on the longer side, but each sentence carries distinct information (exposure_order semantics, not_determinable, disclaimer_md, limit/include_all), with little redundancy.

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

Completeness4/5

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

Even though an output schema exists, the description usefully guards against misreading (exposure_order is an order, not a score; not_determinable must be surfaced; disclaimer_md must reach the user). The one completeness wart is the 'Read-only' claim that conflicts with the readOnlyHint annotation, which could mislead an agent about the tool's side effects.

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%, so the description must carry parameter meaning, and it does: 'limit defaults to 25 (max 100)' and 'include_all adds resolved, dismissed, and out-of-scope rows to the default actionable set.' Only project_id is left unexplained, but its meaning is self-evident as a required identifier.

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 ('Read a project's legal exposure findings, worst exposure first') and implicitly distinguishes itself from run_legal_exposure_review by noting it 'works even while the trigger is closed for the project.' An agent can tell this is the read side of the legal-exposure pair 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 Guidelines3/5

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

The description gives clear context for when this is useful (reading findings, even when the review trigger is closed) and explains that include_all widens the default actionable set. However, it never explicitly names run_legal_exposure_review as the tool to start a review or states when NOT to call this, so routing is left to inference.

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.