RegLayer Instant Decision Briefs

Get structured Check

get_check_result

Read-onlyIdempotent

Retrieve the structured Check result after status reaches 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.
`result`	No	The complete structured Decision Brief when research is ready.
`status`	No	The current order state, such as researching, ready, or failed.
`message`	No	A human-readable status, authentication, or not-ready message.
`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.
`result_kind`	No	The type of structured artifact returned.
`published_at`	No	The timestamp when the result became available.
`delivery_mode`	No	The asynchronous delivery pattern used for this order.
`result_version`	No	The version of the stored structured result.
`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.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the readiness precondition and the structured nature of the result, but it does not disclose behavior when called before ready or error/response characteristics. 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?

The description is a single, well-structured sentence with the action front-loaded and the condition appended. Every word contributes meaning, with no redundant or filler content.

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?

The presence of an output schema reduces the need to explain return values, but the description fails to connect to sibling tools like get_check_status or prepare_check_request to clarify parameter provenance and workflow sequencing. It is minimally sufficient but leaves notable gaps for an agent unfamiliar with the tool family.

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% and the description never mentions order_id or access_token. The agent must rely solely on parameter names and the pattern/minLength constraints, with no guidance on how to obtain these values or how they relate to prepare_check_request. The description does not compensate for the schema gap.

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 uses a specific verb ('Retrieve') and a specific resource ('structured Check result'), and the qualifier 'structured' distinguishes it from siblings like get_check_pdf and get_check_status. The phrase 'after status reaches ready' adds a precise precondition, making the tool's purpose immediately clear.

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 provides clear usage context by stating the result should only be retrieved after status reaches ready, implicitly guiding the agent to check status first. However, it does not explicitly name alternatives such as get_check_status or get_check_pdf, nor does it state when not to use this tool.

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?