FrankoX

external_business_handshake

Idempotent

Submit public non-binding business intent after creating a public ingress session. Send its credential in X-FrankoX-Session header. Never customer/OAuth access. No automatic Opportunity. See /external-agents/skill.md.

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": {
      "message_id": "<message_id>",
      "content": "<content>",
      "public_data_only": "<public_data_only>",
      "session_id": "<session_id>"
    },
    "name": "external_business_handshake"
  }
}

Input Schema

Name	Required	Default
`intent`	No	UNKNOWN
`content`	Yes
`product`	No
`quantity`	No
`authority`	No	UNVERIFIED
`geography`	No
`message_id`	Yes
`session_id`	Yes
`public_data_only`	Yes
`identity_disclosure`	No	WITHHELD
`represented_company`	No
`external_thread_reference`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond annotations (write, idempotent, non-destructive), it discloses that the intent is non-binding, that no Opportunity is auto-created, and that a session credential must go in the X-FrankoX-Session header. These are meaningful behavioral traits not captured by the structured fields.

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?

Four terse, front-loaded sentences; the scoping and credential constraints come first. Pointing to /external-agents/skill.md and the header name are efficient. Slightly telegraphic, but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter mutation tool with 0% schema coverage and no output schema, the description leaves parameter meanings and return behavior entirely to an external doc. 'See /external-agents/skill.md' defers the detail rather than supplying enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, so the schema names fields but explains none. The description adds no meaning to intent, content, product, authority, or identity_disclosure semantics, leaving most parameter intent unexplained.

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?

States a specific verb and resource ('Submit public non-binding business intent') with scope ('after creating a public ingress session'). The 'external/public' framing helps distinguish it from internal request siblings like initiate_network_request, though it doesn't explicitly name them.

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?

Provides a clear prerequisite ('after creating a public ingress session') and an exclusion ('Never customer/OAuth access'), which tells the agent when this path is and isn't valid. It stops short of naming a specific alternative among siblings for the internal case.

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

All FrankoX 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?