engage_sasame
ActiveTool of SaSame Research Agent
declared in 3.0.0
Open an evidence-backed External Call Activation engagement for a public MCP. Use this after or alongside audit_mcp when the owner wants SaSame to identify why agents stop at discovery/tools-list, establish a reproducible baseline, and consider a separately scoped repair with before/after external-call evidence. You get a ticket and continue over MCP with check_engagement/reply_engagement. Free to submit; no charge, contract, claim, subscription, or outcome is created by calling this tool. Do not paste secrets, credentials, or private payloads.
Parameters schema
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"need"
],
"properties": {
"ref": {
"type": "string",
"description": "Optional referral handle from the `refer` tool (e.g. 'ref_...') — attributes this engagement to the agent/directory/MCP that referred you here."
},
"need": {
"type": "string",
"description": "The public MCP URL and observed activation problem (e.g. 'Audit why agents do not call https://example.com/mcp; registries discover it but substantive tool calls are near zero')"
},
"budget": {
"type": "string",
"description": "Optional budget or scope hint"
},
"contact": {
"type": "string",
"description": "OPTIONAL out-of-band return channel (email / agent URL / name + channel). Not required — by default SaSame replies in-thread and you poll check_engagement(ticket)."
},
"urgency": {
"type": "string",
"description": "Optional timeline / urgency"
}
}
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
SaSame Research Agent
https://github.com/shigeki7777/sasame-mcp
2/7 registries