@devries-cameron20 / composio Mirror · read-only / commits / edc10fee9
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

fix(docs): preserve saved tool tag section links

Brendan O'Leary committed Nov 4, 2026 at 14:33 UTC edc10fee90fb94eacb1e01c26315718842efc846
2 files changed +27
docs/content/docs/governance/tool-hints.mdx
+6
@@ -6,6 +6,8 @@ keywords: [tags, readOnlyHint, createHint, updateHint, destructiveHint, governan
6
7 Every tool has a **hint** that describes the action it takes: reading, creating, updating or deleting. In [sessions](/docs/configuring-sessions), you can use these hints to configure the tools available in the session.
8
9 +<span id="tags" className="block scroll-m-28" />
10 +
11 ## Hints
12
13 | Hint | The tool | For example |
@@ -15,10 +17,14 @@ Every tool has a **hint** that describes the action it takes: reading, creating,
17 | `updateHint` | Changes something that already exists, such as its content or settings. It doesn't delete anything. | Edit an issue, rename a file |
18 | `destructiveHint` | Deletes something, such as a file, record or repository. A tool that can delete something has this hint, even if it also creates or updates. | Delete a file, delete a repository |
19
20 +<span id="how-tools-are-tagged" className="block scroll-m-28" />
21 +
22 ## How tools get hints
23
24 Composio assigns hints on a best-effort basis, based on each tool's description and behavior. For MCP tools, Composio infers them from the tool's description and the hints the MCP server provides.
25
26 +<span id="using-tags-in-a-session" className="block scroll-m-28" />
27 +
28 ## Using hints in a session
29
30 A session can allow, block or require approval for tools by their hint, and override this for specific toolkits:
docs/tests/integration/redirects.test.ts
+21
@@ -85,3 +85,24 @@ describe("Redirects - destinations are valid", () => {
85 expect(failures).toEqual([]);
86 });
87 });
88 +
89 +describe("Redirects - saved tool tag section links", () => {
90 + test("legacy anchors survive the redirect alongside the renamed headings", async () => {
91 + const res = await fetchPage("/docs/tool-tags", { timeout: 30_000 });
92 + const html = await res.text();
93 +
94 + expect(res.status).toBe(200);
95 + expect(new URL(res.url).pathname).toBe("/docs/governance/tool-hints");
96 +
97 + for (const id of [
98 + "tags",
99 + "how-tools-are-tagged",
100 + "using-tags-in-a-session",
101 + "hints",
102 + "how-tools-get-hints",
103 + "using-hints-in-a-session",
104 + ]) {
105 + expect(html).toContain(`id="${id}"`);
106 + }
107 + });
108 +});