Skip to main content
Glama

site

by com.dataroompicker

Submit an ENQUIRY to human providers (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Data Room Picker — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to virtual data room providers, who'll contact me directly."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Happy for my details to go to virtual data room providers, who'll contact me directly.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

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

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the stateful two-step flow, the required consent wording, the email with a click link, and the fact that providers only see the enquiry after the person clicks the link.

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 well structured: purpose first, then step 1, then step 2. Every sentence earns its place, including the consent quote, which is essential for correct invocation.

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 complex two-step submission flow and no output schema, the description fully explains what is returned (summary, consent line, confirmation token) and what happens after submission (email, link click, provider visibility). Nothing critical is missing.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds important meaning by linking answers to enquiry_fields keys, requiring consent=true, and defining confirmation as the token returned from step 1 after the person approves the summary. This goes well beyond the bare schema.

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 states a specific action ('Submits an enquiry') and resource ('Data Room Picker'), immediately distinguishing it from a purchase or quote. It also names the two-step nature of the operation, which sets it apart from the sibling comparison and description tools.

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?

The description gives explicit step-by-step call conditions: call first with answers and consent=true, show the summary, then call again only if the person agrees, using the confirmation token. It also clearly states what this tool is not for: not a purchase and not a guaranteed quote.

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

All site toolsInspect
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

A3.7/5.0
Disambiguation4/5

The compare_* tools are clearly separated by purpose: criteria definitions, option lists, and the full table. The enquiry_* tools are also distinct, though compare_options and compare_table could be slightly confused since both return option-related information.

Naming Consistency4/5

The set uses a mostly consistent pattern: compare_* for comparison data and enquiry_* for enquiry-related operations, with submit_enquiry following verb_noun style. The two prefixes are logical but not perfectly uniform across the whole set.

Tool Count5/5

Six tools is well-scoped: three cover the comparison side and three cover the enquiry workflow. Every tool serves a clear, non-redundant role in the site's apparent purpose.

Completeness5/5

The comparison tools cover criteria, options, and the full table, giving agents everything needed to present or filter the comparison. The enquiry tools cover explanation, field schema, and two-step submission, so the main user journey has no obvious dead ends.

Resources