RegLayer Instant Decision Briefs

Get Check PDF URL

get_check_pdf

Read-onlyIdempotent

Return the authenticated PDF endpoint after the Check is ready.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_id`	Yes
`access_token`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	Whether the private status request succeeded.
`error`	No	A machine-readable error label when the request cannot be completed.
`notice`	No	The notice that must travel with RegLayer research outputs.
`status`	No	The current order state, such as researching, ready, or failed.
`message`	No	A human-readable status, authentication, or not-ready message.
`pdf_url`	Yes	The authenticated endpoint for downloading the finished PDF.
`product`	No	The purchased Instant Brief product code.
`brief_id`	No	The Decision Brief identifier used in the finished artifact.
`order_id`	No	The private RegLayer order identifier.
`reference`	No	The customer-facing brief reference.
`api_version`	No	The version of the RegLayer agent delivery contract.
`delivery_mode`	No	The asynchronous delivery pattern used for this order.
`authentication`	Yes	The authorization header required to download the PDF.
`poll_after_seconds`	No	Seconds to wait before the next status check, or null when no further polling is needed.
`connection_required`	No	Whether the original connection must remain open.
`delivery_instructions`	No	Instructions for retrieving the result without relying on email.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedAug 26, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotations already establish the read-only, idempotent, open-world, non-destructive nature. The description adds meaningful context beyond those flags by specifying that the return value is an authenticated PDF endpoint and that readiness is a precondition. There is no contradiction with annotations.

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?

A single front-loaded sentence with no filler. Every element—'authenticated', 'PDF endpoint', 'after ready'—adds necessary information without redundancy.

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

Completeness3/5

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

With a rich input schema, strong annotations, and an output schema present, the minimal description covers the core need. The main gap is the absence of guidance for the not-ready case and no explicit statement that both order_id and access_token are required, though the schema supplies that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 compensate for the parameters. It only indirectly alludes to them: 'Check' maps to order_id and 'authenticated' maps to access_token. It does not explain how the parameters are used, the required patterns, or the meaning of the returned endpoint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Return'), the resource ('PDF endpoint'), and the domain ('Check'), which is enough to tell it apart from the instant-brief siblings. It does not explicitly contrast it with get_check_result or get_check_status, so it stops short of a 5.

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?

'after the Check is ready' gives an explicit timing condition, implying this tool should only be called once readiness is confirmed. However, there is no guidance on when to prefer this over get_check_result or get_check_status, and no mention of what to do if the Check is not ready.

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

All RegLayer Instant Decision Briefs tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

The paired get_check_* and get_instant_brief_* tools are clearly separated by product prefix, and prepare_* tools have distinct purposes. The only slight overlap is list_reglayer_products, which appears to be the broader catalog containing the Instant Brief products listed by list_instant_brief_products.

Naming Consistency5/5

Every tool follows a predictable verb_noun pattern with get_, list_, and prepare_ prefixes and product-specific suffixes. The Check and Instant Brief groups are symmetrically named, making the API surface easy to navigate.

Tool Count5/5

Ten tools is well-scoped for a dual-product regulatory research server. Each tool covers a distinct step in the workflow: product discovery, request preparation, status polling, result retrieval, and PDF download.

Completeness5/5

The tool surface forms a complete workflow: list products, prepare a purchase request, poll status, then retrieve structured results and authenticated PDFs. No obvious dead ends or missing operations within the stated domain.

Resources

Need Help?