[CARE: DEV] Deploy planetary tools as MCP (via fastmcpcloud)

[NISH1001]

What

WE need to convert existing tools @bernardbenson and @bishwaspraveen was working on to proper AKD-compatible tool and deploy

Why

To make the MCP available functionally to agents

How

Convert to akd-ext compatible tools and use fastmcpcloud auto deploy option

cc: @iamsims

[iamsims]

As per discussed with bernard:

We have these tools:

-> pds_catalog_mcp
-> pds4
-> ode
-> img mcp
-> opus_mcp
-> pds4
-> ppi
-> sbn

in which ppi and img is not production ready.

So i ported these code to akd-ext and pushed it in a fork of the repository :
https://github.com/iamsims/akd-ext
and this has been hosted in fastmcp-cloud which is in my personal account:
https://complex-chocolate-python.fastmcp.app/mcp (auth required)

[NISH1001]

@iamsims once ready, do create a PR to merge to upstream. it probably needs module/namespace refactoring as well..like akd_ext/tools/planteary or something? or whatever makes sense semantically

[iamsims]

oh okay dai

[iamsims]

The issue with this mcp changes is however that we have about 25+ tools for PDS, and feels like it will pollute the whole pipeline now we could always unselect the tools but they are way too much of it even to just unselect. @NISH1001 any thoughts on that

[NISH1001]

I was thinking akd-ext to have some semantic namespace. eg: EIE is doing with veda here: NASA-IMPACT/akd-ext#27 (comment)

[NISH1001]

Todo:
Fix the tooling with strict types to reduce possible LLM errors.