termix_snippets_get_all_snippet_foldersRetrieve all snippet folders for the authenticated user to organize and manage code snippets. Use this to list existing folders before creating or assigning snippets.
Get all snippet folders. Retrieves all snippet folders for the authenticated user.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the meaningful context that results are scoped to the authenticated user, but it does not disclose ordering, pagination, or whether the response includes nested snippets.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded, but the first sentence duplicates the tool title almost verbatim. The second sentence adds only the 'authenticated user' scope, so one sentence is largely redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list operation with no parameters, this is near-adequate. However, there is no output schema, and the description does not clarify what shape 'all snippet folders' takes or how it differs from the export/get-all-snippets sibling tools, leaving some ambiguity for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes no parameters, so the empty schema fully documents the input surface. The description's mention of the authenticated user is an auth-context note rather than a parameter, so the baseline 4 for zero-parameter tools applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action and resource: 'Get all snippet folders' and clarifies scope to 'the authenticated user'. It is unambiguous, though it does not explicitly distinguish itself from sibling tools like termix_snippets_export_all_snippets_folders_as_json or termix_snippets_get_all_snippets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus its alternatives. The description merely restates the operation without mentioning exclusions or sibling tools such as exporting folders as JSON or getting all snippets.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.