Skip to content

Docs update from nexus-next #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tmsdkeys merged 1 commit into from
May 12, 2025
Merged

Docs update from nexus-next #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion nexus-next/tool.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ Each Tool must provide a standardized definition, telling us where and how to in
"fqn": "{domain}.{name}@{version}",
"type": "onchain/offchain",
"url": "{url/move_ident}",
"description": "A UTF-8 string",
"input_schema": "draft-2020-12 JSON schema",
"output_schema": "draft-2020-12 JSON schema"
}
Expand All @@ -34,7 +35,12 @@ This will determine _how_ the Leader contacts the Tool. For offchain Tools, this

Onchain Tools will require a similar `url` but it would likely be a move call definition in the format `pkg_id::module::fn` or similar. Confirmation will follow soon.

4. `input_schema` and `output_schema`
4. `description`

A description of what the tool does. Currently we do not enforce a maximum length but this is
subject to change. In addition we assume a UTF-8 representation.

5. `input_schema` and `output_schema`

These will be `draft-2020-12` JSON schema definitions of the Tool inputs and outputs. This lets the Leader parse and verify data going in and coming out of the Tool.

Expand Down