Skip to main content
Glama
morfiade-app

io.github.morfiade-app/morfiade-mcp

Official
by morfiade-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sync_sets

Manage line-based value sets for distributing data across windows. List sets with line counts or create new sets by providing a name and lines.

Instructions

Value sets for distributing across windows: lists of emails, logins or any line-based data, one line per window. Without arguments lists the sets with their line count and how many lines are still free; the values themselves are never shown. With name and lines creates a new set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for a new set; give together with lines
linesNoValues for the new set, one per window: emails, logins, any line-based data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • changedInput schema / properties / lines / description
      Previous value: -"Values line by line, one per window"New value: +"Values for the new set, one per window: emails, logins, any line-based data"
    • addedInput schema / properties / name / description
      Added value: +"Name for a new set; give together with lines"
  2. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

The description usefully discloses that listing shows line count and free lines and that values are 'never shown'. However, with all annotations false, it leaves create-mode behavior vague: what happens if a set name already exists, whether creation returns a result, or whether sets can be modified later.

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

Conciseness5/5

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

Two sentences with no wasted words. The core purpose and both invocation modes are front-loaded, and the critical safety-relevant detail that values are never shown is included.

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

Completeness3/5

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

With no output schema and no annotation support, the description partially compensates by describing list output. It remains incomplete for the create path: no mention of duplicate-name behavior, any errors, or what creation returns.

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

Parameters3/5

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

Schema coverage is 100%, with descriptions already explaining name and lines, including 'one per window. The description mostly restates the same parameter semantics and domain examples, adding only the 'line count/free lines' detail that is more about output than parameters.

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 identifies the resource ('value sets for distributing across windows') and gives specific behaviors: list existing sets with line counts/free lines, or create a new set with name and lines. It is clear enough to distinguish 'sets' from sibling tools like sync_windows or sync_insert, though it never names an alternative explicitly.

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

Usage Guidelines4/5

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

The description clearly explains the two usage modes: no arguments for listing, and name plus lines for creating. This is clear practical context, though it does not explicitly say when to prefer a sibling tool over sync_sets.

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