jira server (Atlassian remote MCP): --example returns {} for body/parent; tool help references operations not exposed as tools #17

Context

Authoring a Confluence page through mcpx jira createConfluenceContent (Atlassian remote MCP v2) hits two mcpx-side gaps in the same flow. Reproduced on mcpx 1.6.0 with mcp-remote bridging the public https://mcp.atlassian.com/v2/mcp endpoint. Both force hand-assembly of the call; filed as one issue since they surface together, but they have separate root causes and can be closed independently.

1. --example emits empty {} for schemaless json{} params

$ mcpx jira createConfluenceContent --example
{
  "body": {},
  "cloudId": "<string>",
  "contentType": "<string>",
  "contentWidth": "narrow",
  "draft": false,
  "parent": {},
  "private": false,
  "title": "<string>"
}

body and parent are {"type":"object"} with no properties in the server's input schema, so the example generator has nothing to skeletonize. The actual shapes exist only as prose in --help (format is html or markdown, value is the content string; Use { "spaceId": "<numeric-space-id>" } for parent). mcpx jira updateConfluenceContent --example has the same gap: "body": {} and "edits": [null].

Suggested fix: when a json{}/json[] param's schema has no properties, fall back to the param's own description — extract the first embedded JSON object (the parent description literally contains { "spaceId": ... } examples) or render a shape hint like json{format, value} for body. A config-level per-tool/per-param example override would also cover server-side cases the generator cannot infer.

2. Tool help references operations that are not exposed as tools

createConfluenceContent / updateConfluenceContent descriptions (passed through from the server) mandate calling getConfluenceSpace and getContentFormatGuide before authoring. Neither appears in mcpx list jira -v — they are only reachable as generic operations via executeRead. Both verified working:

mcpx jira executeRead --cloudId <cloudId> --name getConfluenceSpace --inputs '{"spaceIdOrKey": "<space-key>"}'
mcpx jira executeRead --cloudId <cloudId> --name getContentFormatGuide --inputs '{"toolName": "createConfluencePage"}'

An agent following the help text concludes the referenced tools do not exist (nothing named getConfluenceSpace is callable as a tool) and authors content without loading space instructions.

Suggested fix: either rewrite the "through execute with name=X" phrasing when rendering help (state the executeRead/executeWrite invocation directly), or support a config-level per-tool description override/append so users can document the indirection without patching mcpx.

Repro

Any project with the Atlassian remote MCP v2 configured, then:

mcpx jira createConfluenceContent --example
mcpx jira createConfluenceContent --help
mcpx list jira -v   # no getConfluenceSpace / getContentFormatGuide tools