NASA-IMPACT / NASA-IMPACT/akd-core
PSI Agent: Tool Development (fast-iteration build via akd-ext)
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
PSI Agent: Tool Development
Tracking · Parent EPIC: #377 — PSI Agent · Tool scope: #500 · PI: 26.4 Agent Development
Collaboration: NASA PSI (Physical Science Informatics) team
Context
Once the tool scope is agreed (#500), the PSI agent's tools need to actually get built. This issue covers that build — deliberately starting fast and lightweight so we can iterate on tool behavior with the PSI team before committing to a permanent home.
The build happens in nasa-impact/akd-ext (the misc extension space to akd-core). Using akd-ext lets us prototype, wire up, and test tools quickly against real PSI workflows without being blocked on the "where do these live long-term" question — that is handled separately in the hosting/deployment issue (#504).
What this issue covers
- Implement the PSI agent tools defined in the tool scope doc (#500), inside
nasa-impact/akd-ext. - Make each tool callable by the PSI agent end-to-end, via the agreed interface (e.g. MCP tool).
- Iterate quickly on tool inputs/outputs and behavior against representative PSI data/workflows.
- Validate each tool does what the scope intends — enough to demo and collect PSI feedback.
Done when
- Tools from the #500 scope doc implemented in
nasa-impact/akd-ext. - PSI agent can invoke the tools end-to-end (interface per scope doc, e.g. MCP).
- Tools exercised against representative PSI data/workflows; behavior validated with the PSI team.
- Learnings and any interface changes fed back into the scope doc.
- Ready to hand off to the hosting/deployment decision (#504).
Depends on
- #500 — tool scope document (defines what to build). Build can begin per tool as soon as its scope is firm.
Out of scope
- Permanent hosting / deployment of the tools — where they ultimately run is a separate PSI↔AKD decision, tracked in #504. akd-ext here is a fast-iteration staging ground, not the final home.
- Full-agent scope (agent hosting, agent ownership) — broader EPIC #377 concern.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the tool scope document in issue #500, then inspect nasa-impact/akd-ext to find its extension and agent-integration entry points. Implement the scoped tools there, exercise them against representative PSI workflows, and verify end-to-end invocation and feedback-driven interface updates before handoff to #504.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100