Skip to main content
Glama

Prepare an inquiry to i22

i22_ai_inquiry_preview
Read-onlyIdempotent

Step 1 of 2 for sending an inquiry to the responsible i22 team on behalf of the person you are helping. Sends nothing: returns a summary and a confirmation token. Show the person the summary, and call i22_ai_inquiry_send only after they confirm it. All fields come from the person; never invent them.

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": {
      "topic": "<topic>",
      "company": "<company>",
      "name": "<name>",
      "role": "<role>",
      "email": "<email>",
      "message": "<message>",
      "next_step": "<next_step>"
    },
    "name": "i22_ai_inquiry_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the person sending the inquiry.
roleYesRole or job title of the person at the company.
emailYesE-mail address of the person; the team replies to it. No confirmation mail is sent to it.
topicYesSlug of the service the inquiry is about, from i22_ai_services_list (e.g. agentic-transformation), or "unclear" when no service fits.
companyYesCompany the person works for.
messageYesThe inquiry in the person's own words.
next_stepYesDesired next step: callback (phone call), meeting or documents (send documents).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Adds meaningful behavior beyond annotations: it sends nothing, returns a summary and confirmation token, and requires human confirmation before proceeding. It does not explain token lifetime or summary contents, but annotations already establish read-only, idempotent, non-destructive behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the step role and no-send behavior, followed by the confirmation workflow and data-source constraint. No wasted wording.

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?

Complete enough for the agent to gather real values, preview the inquiry, show the summary, and defer sending until confirmation. Minor gaps remain around what the summary/token contain and how the token is supplied to the send step, but no output schema is provided and annotations cover safety traits.

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 the schema already documents each field. The description adds an important data-provenance rule: all fields come from the person and must never be invented.

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 action and resource: it is step 1 of 2 for sending an inquiry to the responsible i22 team, and it sends nothing. It clearly distinguishes itself from i22_ai_inquiry_send by framing itself as the preview/confirmation step.

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?

Explicitly says to show the person the summary and to call i22_ai_inquiry_send only after they confirm it. The sequencing and confirmation gate leave little ambiguity about when this tool is used versus the send tool.

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