Skip to main content
Glama

Submit an ENQUIRY to Growth Shares Valuation (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Growth Shares Valuation: 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 Growth Shares Valuation team sees it. Consent means the person has read and agreed to: "I agree that the team behind this growth shares site may read my question and pass it to a tax adviser or share valuer."

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: I agree that the team behind this growth shares site may read my question and pass it to a tax adviser or share valuer.
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.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: it discloses that step 1 only validates and returns a summary plus token, that step 2 actually submits, that the enquirer must click an emailed link before the team sees it, and that data may be passed to a tax adviser or share valuer. It also spells out what consent means, which is the crux of the tool's side effects.

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?

Front-loaded with the most important disambiguation (not a purchase) followed by an ordered Step 1 / Step 2 structure that mirrors the call sequence. The consent sentence is repeated in the schema, but that repetition is defensible because the text must be shown verbatim to the person.

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 stateful, two-call, consent-bearing tool with nested parameters and no output schema, the description covers sequencing, expected returns per step, the consent wording, and the downstream email-verification path. Only minor edge cases (e.g. validation failure in step 1) are unaddressed.

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. The description goes beyond the schema by explaining that answers are keyed by field key from enquiry_fields and that confirmation is the step-1 token used only after the person approves the summary — flow-level meaning the schema alone does not convey.

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 Growth Shares Valuation") and immediately disambiguates with "NOT a purchase, NOT a guaranteed quote". It also references the enquiry_fields sibling as the source of field keys, so an agent can place it relative to the other tools without opening a 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?

Gives an explicit two-step sequence with the condition that gates step 2 ("only if the person agrees") and the exact arguments required at each step. It also states what must be shown to the user between steps, leaving nothing about when/how to call to inference.

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