feat(tools-registry): update tako-search entry - #18380
Open
25eliu wants to merge 1 commit into
Open
Conversation
The @takoviz/ai-sdk package exports three tools (takoSearch, takoAnswer, takoContents), but the description covers only search. Restates it to describe the package. Also repoints two links: docsUrl went to the GitHub README rather than the AI SDK integration guide on docs.tako.com, and apiKeyUrl went to the site root rather than the API keys page. The slug is unchanged so /resources/tools/tako-search keeps working.
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrects three fields on the existing
tako-searchentry incontent/tools-registry/registry.ts. No new entry, no new page — the listing already exists and renders at /resources/tools/tako-search.Changes
descriptiontakoSearchonlydocsUrlgithub.com/TakoData/ai-sdk#readmedocs.tako.com/documentation/integrations/vercel-ai-sdkapiKeyUrlhttps://tako.comhttps://tako.com/console/api-keysdescription—@takoviz/ai-sdkexportstakoSearch,takoAnswer, andtakoContents. The current text describes only the first, so the card understates the package.docsUrl— this is the card's "Learn More" link, and it currently lands on a GitHub README. Repointed at our AI SDK integration guide, matching how neighbouring entries link to a vendor-hosted integration page (exa→docs.exa.ai/reference/vercel,tavily→docs.tavily.com/documentation/integrations/vercel,firecrawl→docs.firecrawl.dev/integrations/ai-sdk,valyu→docs.valyu.ai/integrations/vercel-ai-sdk).apiKeyUrl— this is the "Get API Key" button. The site root leaves the reader to find the key page themselves; this links directly to it.Deliberately unchanged
slugstaystako-search, so the existing/resources/tools/tako-searchURL keeps working.codeExampleis already correct — it importsisStepCountand typechecks againstai@7.0.0. Left alone.model: 'openai/gpt-5.2'is current and used by other entries in the file.Verification
registry.tstypechecks after the edit.oxfmtrc.jsonc(singleQuote: true; the old value needed double quotes only for an apostrophe, which the new text doesn't contain)main, independent of docs: add Tako community provider #18355Related
#18355 proposed a full community-provider page for Tako. I've parked that as a draft — the tools registry looks like the right home for a tool-only package, and this PR makes the existing entry point at the documentation instead of duplicating it.