Skip to content

Conversation

@teallarson
Copy link
Contributor

@teallarson teallarson commented Feb 2, 2026

Contains docs updates that align with the changes in the toolkit picker here and here.

This should ideally not be merged until approximately when those changes go live.

@vercel
Copy link

vercel bot commented Feb 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Feb 2, 2026 2:53pm

Request Review

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style Review

Found 4 style suggestion(s).

Powered by Vale + Claude

teallarson and others added 4 commits February 2, 2026 09:42
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
- Optimized tools

The distinction is merely a matter of how they are designed. Both types of tools can be used seamlessly in the same way. There is no difference in their interfaces, the way they are called, or how you interact with them through the Arcade [Dashboard](https://api.arcade.dev/dashboard/) or the Arcade [SDK clients](/references).
The distinction is merely a matter of how Arcade designs them. Both types of tools can be used seamlessly in the same way. No difference exists in their interfaces, the way they are called, or how you interact with them through the Arcade [Dashboard](https://api.arcade.dev/dashboard/) or the Arcade [SDK clients](/references).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how Arcade designs them

This was a vale suggestion, but I think we have some community contributions so this isn't quite true always? Except maybe it is because the Optimized ones are optimized by us?

Since they require careful design and evaluation, Optimized tools take time and effort to build. Arcade understands that your Agent or chatbot project might need capabilities not yet covered by Arcade's Optimized MCP Servers. For this reason, Arcade also offers low-level Unoptimized MCP Servers (formerly known as Starter MCP Servers).

## Starter tools
<span id="starter-tools" />
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was a weird suggestion from Cursor to not break existing links. It's clever I guess, but I'm not sure it's right.

**Toolkits**

- `[feature - 🚀]` Introduce [Starter Tools](/guides/create-tools/improve/types-of-tools), a new type of tool that mirrors the original HTTP API design of the upstream service.
- `[feature - 🚀]` Introduce [Unoptimized tools](/guides/create-tools/improve/types-of-tools), a new type of tool that mirrors the original HTTP API design of the upstream service.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we want to back-edit the changelog...


#### Starter tools
<span id="starter-tools" />

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

again with clever link stuff

@teallarson teallarson changed the title docs: rename Starter tools to unoptimized docs: rename Starter tools to Unoptimized Feb 2, 2026
@teallarson
Copy link
Contributor Author

@nearestnabors this PR is blocked on the monorepo updates, but the content is worthy of a review in the meantime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants