Skip to main content
Glama

site

by com.takehomecompass

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

submit_enquiry

Submits an enquiry to Take-Home Compass — 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: "By submitting you agree Take-Home Compass may reply to your question by email. We do not sell your details to anyone."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: By submitting you agree Take-Home Compass may reply to your question by email. We do not sell your details to anyone.
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

A4.9/5.0
Behavior5/5

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

No annotations are present, so the description carries full burden. It discloses side effects: no purchase, no guaranteed quote, email sent, provider only sees enquiry after link click, and consent text with no data selling.

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?

Well-structured and front-loaded with purpose and steps, but the consent text is repeated verbatim in both the description and the consent parameter description, adding minor redundancy.

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?

No output schema is provided, but the description explains both step outcomes: validation returns summary, consent line, and confirmation token; final submission sends email and requires link click before provider visibility.

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?

All parameters are described: answers are keyed by field key from enquiry_fields, consent has exact required agreement text, and confirmation is the token from step 1. Schema coverage is complete and enriched.

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?

Description clearly states the tool submits an enquiry to Take-Home Compass, with explicit two-step behavior and negative scope (NOT a purchase, NOT a guaranteed quote), distinguishing it from enquiry_describe and enquiry_fields.

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?

Provides explicit step-by-step instructions: step 1 validates and returns a summary/token, step 2 requires confirmation token and person approval. It also tells when consent must be true and references enquiry_fields for field keys.

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

A4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: schema, provenance, exact-row lookup, substring search, multi-value comparison, aggregate stats, top/bottom ranking, and enquiry lifecycle steps. Even the three query tools (dataset_row, dataset_compare, dataset_search) are semantically separate and described with enough precision to avoid misselection.

Naming Consistency5/5

All tools follow a consistent snake_case pattern with a domain prefix: dataset_* for the data exploration tools and enquiry_* for the form workflow. The suffix is sometimes a noun (columns, provenance, fields) and sometimes a verb (search, compare, submit), but the uniform prefix and predictable structure make the set easy to navigate.

Tool Count5/5

Ten tools is a well-scoped size for a server covering two related areas: dataset analysis and enquiry submission. Each tool earns its place; there is no obvious redundancy or bloat, and the split of seven dataset tools and three enquiry tools matches the apparent purpose.

Completeness4/5

The dataset tools cover schema discovery, provenance, filtering, searching, comparison, statistics, and ordering—a solid analytical surface. The only notable gap is a way to retrieve all rows at once without a filter, though that may be intentionally omitted since most queries are targeted. The enquiry tools form a complete describe-fields-submit flow.

Resources