Skip to main content
Glama
Sign In

site

by com.entitysearchhq
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to EntitySearch HQ: 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 EntitySearch HQ emails you the answer to your lookup question and shares nothing else with anyone."

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "answers": "<answers>",
      "consent": "<consent>"
    },
    "name": "submit_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: By submitting you agree EntitySearch HQ emails you the answer to your lookup question and shares nothing else with anyone.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses validation on step 1, the returned summary/consent line/token, and the double opt-in where the person must click an emailed link before any provider sees the enquiry. It does not describe error or failure behavior (e.g. what happens with a stale or invalid confirmation token), which is the main remaining gap for a two-phase submit.

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?

Long but front-loaded and dense: the negative scoping comes first, then step 1, then step 2, then the consent wording. The only mild redundancy is restating the consent sentence that already lives in the consent parameter description, which is defensible for a legal-adjacent prompt.

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?

For a nested-object, mutation-style tool with no output schema and no annotations, the description supplies everything needed to call it correctly: field keying, the two-phase flow, consent semantics, and what the person sees after submission. Nothing essential to a correct invocation is missing.

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 coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: answers must be keyed by field key drawn from enquiry_fields, consent=true is a positive assertion of the person's agreement, and confirmation is specifically the step-1 token used only after approval. That sequencing context is not derivable from the schema alone.

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 ("Submits an enquiry to EntitySearch HQ") and immediately scopes it negatively: "NOT a purchase, NOT a guaranteed quote." That contrast tells an agent how this differs from any purchase/quote flow without needing the sibling schemas.

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?

Gives an explicit two-step protocol plus the gate for each step: step 1 with answers and consent=true, then step 2 "only if the person agrees" with the same answers plus the confirmation token. It also points to enquiry_fields for the answer keys, so the agent knows where the field keys come from.

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
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.

Resources