Skip to main content
Glama
Sign In

site

by com.workingcapitalquotes
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Working Capital Quotes: 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 sending this you agree the Working Capital Quotes team reads your enquiry and replies by email. We do not pass it to anyone else."

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 sending this you agree the Working Capital Quotes team reads your enquiry and replies by email. We do not pass it to anyone else.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: By submitting you agree Working Capital Quotes shares your details with business lenders and funding providers who may contact you."New value: +"true only when the person has agreed to: By sending this you agree the Working Capital Quotes team reads your enquiry and replies by email. We do not pass it to anyone else."
  2. First observed

TDQS

A4.8/5.0
Behavior5/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 so: it discloses that step 1 only validates and returns a summary, consent line, and token, that step 2 actually submits, and that the person must click an emailed link before any provider sees the enquiry. The exact consent text is reproduced, removing ambiguity about what consent=true attests.

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?

It is front-loaded with the core identity and the two steps, and each sentence carries operational weight. The closing verbatim consent quote duplicates the consent field description in the schema, a mild redundancy in an otherwise tight definition.

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 exists, so the description compensates by describing what step 1 returns (summary, consent line, token) and what step 2 produces (an email with a verification link). For a nested-object, two-phase submission tool, nothing an agent needs to call it correctly 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: answers are keyed by field key taken from enquiry_fields, and confirmation is only meaningful on the second call after approval. The flows and provenance of each parameter are clearer than 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?

The definition states a specific verb and resource (submits an enquiry to Working Capital Quotes) and immediately bounds the scope with 'NOT a purchase, NOT a guaranteed quote.' Naming the two-step flow and pointing to enquiry_fields for field keys distinguishes it from the sibling enumeration 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?

It gives explicit sequencing: Step 1 with answers plus consent=true to validate, Step 2 only if the person agrees, using the same answers plus the confirmation token. The when-not case (before the person agrees) is stated directly rather than inferred.

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