Skip to main content
Glama

Request an introduction

request_intro

Sends one introduction email from the user to Brett's team at Optimus, with the user CC'd and reply-to set to them, so either side can reply. Requires the user's explicit consent (consent: true) before it is called. Creates no account and no newsletter signup. Takes the user's email, what they want, and what they shared about their business.

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": {
      "email": "<email>",
      "goal": "<goal>",
      "consent": "<consent>"
    },
    "name": "request_intro"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesWhat they want help with, in their words
nameNo
agentNoWhich agent/client you are, if you can say
emailYesThe human's email address
pillarNoWhich part of the business is tightest
consentYesMust be true: the human said yes to the introduction
businessNoRevenue, team size, what they run

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, so the external side-effect and non-idempotency profile is known. The description adds valuable context beyond that: exactly one email is sent, to a named third party, with CC and reply-to configured, and it clarifies nothing is persisted (no account, no signup). It says nothing about rate limits, failure modes, or what happens if consent is omitted at runtime.

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 action and recipient, then the consent gate, then negative scope. The final sentence restating the inputs is slightly redundant with the schema but is short and does not obscure the essentials.

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?

Seven parameters with high schema coverage and no output schema mean the description does not need to document return values, and it covers the consent gate and side-effect boundary that matter most. The main missing piece is what the caller gets back or how failure to send is signaled, which is a modest gap for an outward-facing send action.

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 86%, so the schema already carries most parameter meaning; baseline is 3. The description maps email, goal and business to plain-language intent and reinforces that consent must be true, but adds no format, length or enum guidance for the remaining fields (pillar, agent, name).

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 one introduction email from the user to Brett's team at Optimus — plus the delivery mechanics (user CC'd, reply-to set) and the negative scope (no account, no newsletter signup). This is clearly distinguishable from siblings like fit_check or describe_optimus.

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

Usage Guidelines4/5

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

Explicitly states the precondition that gates invocation: the user must have given explicit consent (consent: true) before the call. It also clarifies what the tool does not do (no account creation, no newsletter signup), which helps rule out mistaken use. It stops short of naming a sibling tool to run first (e.g. a fit check), so routing among alternatives is implied rather than stated.

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