Emergent Technologies

Hand off to Emergent's team

start_conversation

Read-onlyIdempotent

Prepares a consent-safe handoff to Emergent's team. It sends nothing and saves nothing: it returns a short summary of what the person wants and the exact Emergent page where the person reviews, confirms and submits their own details. Show the person the summary and the link, and send them there only after they say yes.

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": {
      "intent": "<intent>"
    },
    "name": "start_conversation"
  }
}

Input Schema

Name	Required	Description	Default
`intent`	Yes	license_records, refer_businesses, consulting or other
`request`	No	Optional: what the person wants, in a sentence. Returned to you as written; do not include personal details.

Output Schema

Name	Required	Description	Default
`meta`	Yes
`sent`	Yes
`saved`	Yes
`summary`	Yes
`confirmAt`	Yes
`alternative`	Yes
`personRequest`	Yes
`instructionsForCallingAgent`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description still adds real value by stating "it sends nothing and saves nothing" and by disclosing the human-in-the-loop contract — the person reviews and submits their own details on the Emergent page, not through this tool.

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 with the no-side-effect guarantee front-loaded and the follow-up procedure second; every clause carries information and nothing is padded.

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?

An output schema exists, so return values needn't be spelled out, yet the description still characterizes the return as a summary plus an exact URL, which is enough for correct invocation. What remains thin is routing guidance against the sibling tools.

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 both the intent enum and the request field are already documented in the schema. The description adds only the reminder that the request text should avoid personal details and will be echoed back, which is a marginal restatement rather than new meaning.

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?

"Prepares a consent-safe handoff to Emergent's team" gives a specific verb and resource, and the second sentence clarifies the output is a summary plus a destination page rather than a message sent. This is distinguishable in kind from question-answering siblings such as ask_emergent, though no sibling is named explicitly.

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?

It states the operating procedure clearly: show the person the summary and link, and send them there only after they say yes. That gives a concrete gating condition for use of the result. It stops short of naming when to prefer this over siblings like consulting_offer or check_program_fit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Emergent Technologies tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?