Skip to main content
Glama

alisac-it-mcp

submit_inquiry

Submit a structured business or project inquiry to Alisa Chebotarenko on behalf of a user (requires explicit user confirmation and privacy consent).

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>",
      "request_reason": "<request_reason>",
      "preferred_contact": "<preferred_contact>",
      "message": "<message>",
      "privacy_consent": "<privacy_consent>"
    },
    "name": "submit_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emailNo
phoneNo
messageYes
request_reasonYes
privacy_consentYesMust be true after explicit user consent.
preferred_contactYes
telegram_usernameNo
phone_country_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the two most important behavioral traits: this is an outbound submission to a named third party that requires explicit user confirmation and privacy consent. It stops short of saying what happens after submission, whether the data is transmitted externally or stored, or how failures surface.

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?

One front-loaded sentence with the resource and recipient stated before the parenthetical constraints; nothing is padded. The parenthetical is dense but each clause is meaningful.

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

Completeness2/5

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

For a nine-parameter, five-required mutation with no annotations and no output schema, the definition is thin: it does not explain the conditional field pairs, what 'request_reason' should contain, or what the caller learns on success. The consent caveat is the only real completeness win.

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

Parameters2/5

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

Schema description coverage is 11% — only privacy_consent is documented — and the description compensates for almost none of it. Eight parameters (name, email, phone, message, request_reason, preferred_contact, telegram_username, phone_country_code) get no semantic help, and the description never explains the obvious conditional relationships, such as telegram_username being relevant only when preferred_contact is 'telegram' or phone_country_code pairing with phone.

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 description names a specific verb ('Submit'), a specific artifact ('structured business or project inquiry'), and the recipient ('Alisa Chebotarenko'), which is far more than the tool name alone conveys. It implicitly distinguishes itself from the read-only siblings (get_profile, list_case_studies, list_services) by being the only submission path, though it never explicitly says so.

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?

It states a precondition for use ('requires explicit user confirmation and privacy consent') but never frames when to reach for this tool versus the other listed tools, nor what to do if the user has not consented. Usage is implied rather than guided.

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.