Skip to main content
Glama

TWVS — Industrial Valves & Engineering Supply Catalog

Submit Consultation Inquiry

submit_consultation_inquiry

Submits an advisory consultation request directly into the TWVS executive pipeline with fail-fast validation. When to use: Call this tool when you specifically need to execute 'submit_consultation_inquiry' on TWVS Advisory & Consulting (twvs.co.za). Do NOT use this tool when another specialized tool fits better (use 'list_practice_areas' or 'get_partner_ecosystem' or 'check_consultation_slots' for their respective operations). Parameters: name (required), company (optional), email (required), phone (required), division (required), interest (required), message (required), preferred_date (optional), preferred_time (optional). Behavior & Side Effects: Creates a live record/session in the backend database; no authentication required for public initiation; rate-limited to 60 requests/min per IP. Returns: Structured JSON object containing status, matched records or computed metrics, and canonical action URLs.

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": {
      "name": "<name>",
      "email": "<email>",
      "phone": "<phone>",
      "division": "<division>",
      "interest": "<interest>",
      "message": "<message>"
    },
    "name": "submit_consultation_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of requesting executive or representative. [Required: non-empty valid value must be supplied].
emailYesBusiness email address of the requester. [Required: non-empty valid value must be supplied].
phoneYesDirect contact telephone number. [Required: non-empty valid value must be supplied].
companyNoOptional institution, hospitality group, or business name.
messageYesSpecific operational challenge, project scope, or advisory requirements. [Required: non-empty valid value must be supplied].
divisionYesTarget TWVS practice division (TV Consulting, WV Consulting, or General Advisory). [Required: non-empty valid value must be supplied].
interestYesPrimary advisory discipline (e.g. Capital Markets, ISO 20022, Reconciliations, API Security, Restaurant Costing). [Required: non-empty valid value must be supplied].
preferred_dateNoOptional preferred consultation date in YYYY-MM-DD format.
preferred_timeNoOptional preferred time window (e.g. 10:00 AM - 12:00 PM SAST).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations it discloses that a live record is created in the backend database, that no authentication is needed for public initiation, and that the endpoint is rate-limited to 60 requests per minute per IP. Those are exactly the operational facts an agent needs before committing a write that is neither idempotent nor destructive.

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 purpose is front-loaded in the first sentence and the block structure (purpose / when to use / parameters / behavior / returns) is easy to scan. It loses points for the redundant full parameter recital and the circular when-to-use sentence, both of which consume space without adding information.

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?

For a nine-parameter mutation with no output schema, the definition covers side effects, authentication, rate limits, and a return shape, which is close to complete. The return description ('matched records or computed metrics') reads as repurposed generic copy and does not clearly describe what a submission actually returns, such as a reference ID or confirmation status.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents every field including the division enum and the date/time formats. The description merely restates the parameter names with required/optional labels and adds no format, constraint, or validation detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource plus a scope qualifier: a consultation request is written 'directly into the TWVS executive pipeline' with 'fail-fast validation'. An agent can tell this is a write-path intake tool rather than a lookup, though the sibling distinction is only drawn later and in generic terms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The definition does include explicit 'when to use' and 'do NOT use' blocks and names three alternatives (list_practice_areas, get_partner_ecosystem, check_consultation_slots). However, the positive condition is circular boilerplate ('call this when you specifically need to execute submit_consultation_inquiry'), so it never states the real trigger, such as a user wanting to book or request advisory services.

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