Skip to main content
Glama
MatheusAlves96

termix-mcp

by MatheusAlves96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Create a new snippet

termix_snippets_create_new_snippet

Create a new snippet to add reusable commands or notes to your Termix environment. Specify name, content, folder, order, and note type to organize remote operations.

Instructions

Create a new snippet. Creates a new snippet for the authenticated user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
orderNo
folderNo
isNoteNoWhen true, the snippet is a note (copy/paste only, not directly executable on a host).
contentNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate a mutating, non-idempotent operation, and the description adds the useful user-scoping detail. It does not address the openWorldHint or explain side effects, but it does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a near-exact repetition of the title, and the second adds only minimal value. The redundancy wastes a sentence without offering meaningful detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with 6 optional parameters and no output schema, the description omits parameter semantics, return behavior, and usage conditions. The presence of annotations does not fill these gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only 1 of 6 parameters (isNote) has a schema description, and the tool description provides no parameter information at all. With schema coverage at 17%, the description fails to compensate, leaving name, order, folder, content, and description semantics unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Create a new snippet' and adds 'for the authenticated user', specifying the resource and scope. However, it does not differentiate from sibling tools like update_snippet or create_new_snippet_folder beyond the obvious verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives such as creating a snippet folder or updating an existing snippet. The only hint is the name/verb, with no explicit context or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools