Skip to main content
Glama

Send a confirmed inquiry to i22

i22_ai_inquiry_send
Idempotent

Step 2 of 2: sends the inquiry from i22_ai_inquiry_preview by e-mail to the responsible i22 team. Call it only after the person has confirmed the summary. The same inquiry is sent at most once within 24 hours, and the number of inquiries per sender and per day is limited.

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": {
      "token": "<token>"
    },
    "name": "i22_ai_inquiry_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe confirmation token returned by i22_ai_inquiry_preview.

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?

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the side effect is an e-mail to a named external party, sends are deduplicated within a 24-hour window, and there is a per-sender daily cap. It stops short of saying what a successful or failed call returns, which matters given there is no output schema.

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 'Step 2 of 2' and the verb, followed by the precondition and then the limits. Every clause carries operational information; nothing is redundant.

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 single-token, non-destructive tool with full schema coverage and annotations, the description covers sequencing, the human-confirmation gate, dedup and rate limits. The only gap is the absence of any statement about the result of the send, which is not covered by an output schema.

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% and the token parameter is already documented as the confirmation token from i22_ai_inquiry_preview. The description adds the semantic link that the token implies person-confirmed content, which is more than the schema states, though it does not discuss token expiry or reuse behavior.

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 ('sends the inquiry ... by e-mail to the responsible i22 team') and explicitly positions itself as step 2 of 2 relative to i22_ai_inquiry_preview, so an agent can distinguish it from the preview sibling without reading either 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 precondition ('Call it only after the person has confirmed the summary') and names the sibling whose output feeds it, which is exactly the when/when-not routing an agent needs. The 24-hour dedup window and per-sender daily quota further constrain invocation.

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