Make the Lucid MCP fully transparent: tool reference, roadmap, plus bulk ops and full shape library access

What I want, simply: describe a diagram to my AI agent, give feedback on it, then easily iterate either in the Lucid UI or back through the MCP, while using the proper native AWS resources throughout.

The biggest ask: a fully transparent MCP. I want a published tool-by-tool reference + parameters + a roadmap so users know what's available, what's coming, and what's not planned. Today everything is discovered through runtime trial-and-error.

Here are my problems and proposed solutions / requests:

1. Problem: No public tool / parameter docs or roadmap. Agents discover capabilities by trial-and-error. Users can't tell what's planned vs deprioritized.
   1. Publish a tool-by-tool reference (each name + purpose + parameter signature) plus a quarterly status board (planned / in progress / shipped / not planned).

2. Problem: No bulk update / move. Every position change, resize, or text edit is a separate `lucid_edit_item` call. Updating 20 icons = 20 round-trips. "Shift these 8 boxes down 50px" = 8 round-trips today.
   1. Solution: Add a bulk-edit and bulk-delete primitive that accepts an array of item ops (id + position / size / text) in one call.

3. Problem: `lucid_add_block` rejects AWS / Azure / GCP shape libraries. Only Standard Library block types (RectangleBlock, TextBlock, etc.) are accepted. AWS 2024 / Azure 2024 / GCP 2021 shapes are reachable ONLY via `lucid_create_diagram_from_specification` (`namedShape` + `className`). Passing `ResAmazonVPCEndpointsAWS2024` to `lucid_add_block` returns HTTP 500 "An unknown error occurred". Mid-iteration additions force either full doc recreation (loses the reviewer's stickies and repositioning) or fallback to plain rectangles (loses the AWS visual).
   1. Solution: Extend `lucid_add_block` to accept the classNames listed in `lucid://shape-libraries/aws-2024/*`, `lucid://shape-libraries/azure-2024/*`, `lucid://shape-libraries/gcp-2021/*`, including containers (VPC, AWS Cloud, Region, Subnet)., etc..
4. Problem: no delete. I would love to be able to have access to delete lucid charts that I own. Because of restrictions on lucid edit block actions, I have had to use create new from spec and iterate, so now I have a lot of diagrams that I would like to delete haha.  This is mostly a side effect of the mcp function limitations
   1. Solution: add bulk / expand update capabilities or allow for delete of document to enable iteration

If I'm missing something / if any of this is already doable via a path I haven't found, please point me at it!

Thanks!