Skip to main content
Glama

Submit an ENQUIRY to Hindi AI Trainer Jobs (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Hindi AI Trainer Jobs: 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 the Hindi AI Trainer Jobs team sees it. Consent means the person has read and agreed to: "OK for Hindi AI Trainer Jobs to email me about paid Hindi AI work."

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: OK for Hindi AI Trainer Jobs to email me about paid Hindi AI work.
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
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses that Step 1 only validates and returns a summary plus a confirmation token, that Step 2 actually submits, and that a double opt-in email link must be clicked before the team sees the enquiry. It also quotes the exact consent text required, which an agent would otherwise have to guess.

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?

The critical disqualifier ("NOT a purchase, NOT a guaranteed quote") is front-loaded and the two steps are clearly enumerated. The second sentence is long and packs validation, return values, and a UI instruction together, but nearly every clause is load-bearing.

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

Completeness4/5

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

With no output schema, the description compensates well by describing Step 1's return payload and the post-submission email link. It stops short of saying what a Step 2 response looks like or what happens when validation fails, which matters for a two-call protocol with a nested answers object.

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 ordering semantics the schema cannot express: answers are keyed by field key from enquiry_fields, and the confirmation token must be paired with the same answers on the second call. It does not add typing detail, but the workflow constraint is genuinely extra information.

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 names a specific verb and resource ("Submits an enquiry to Hindi AI Trainer Jobs") and immediately scopes it negatively ("NOT a purchase, NOT a guaranteed quote"), which separates it from any transaction-flavored sibling. It also references enquiry_fields as the source of field keys, so an agent can route between the two without opening the schema.

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?

It spells out a numbered two-step protocol: Step 1 with answers and consent=true, then Step 2 only after "the person agrees," with a human-in-the-loop gate between them. Exclusions around what the tool is not (purchase, guaranteed quote) further pin down when it is appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources