Skip to main content
Glama
morfiade-app

io.github.morfiade-app/morfiade-mcp

Official
by morfiade-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sync_insert

Destructive

Insert each Chrome profile's pinned value into the same focused input across all synced windows. Run sync_spread first to preview value assignments.

Instructions

Type each window's own pinned value into the input field that has the cursor in the leading window; the same field receives it in every window. A person must click into that field first. The text is inserted into the page as typed input and cannot be undone by the tool. Windows without a pinned line get the next free one now; call sync_spread first to review who gets what.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
setYesSet name as sync_sets lists it
leaderNoProfile whose window shows where to type: the field focused there receives the values in every window; defaults to the first ready window

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • changedInput schema / properties / leader / description
      Previous value: -"Lead window; defaults to the first ready"New value: +"Profile whose window shows where to type: the field focused there receives the values in every window; defaults to the first ready window"
    • addedInput schema / properties / set / description
      Added value: +"Set name as sync_sets lists it"
  2. First observedv0.2.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already indicate destructiveHint=true, but the description adds essential detail: the insertion cannot be undone and requires manual field focus. It also explains behavior for windows without a pinned line. These go beyond the annotations and give the agent a precise mental model of side effects.

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

Conciseness4/5

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

The description is compact but dense; every sentence adds value: the main action, the manual precondition, the irreversibility, and the fallback behavior. It is front-loaded with the primary action and avoids redundancy. Slightly complex due to multiple clauses, but efficient.

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

Completeness5/5

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

For a tool with two parameters, full schema coverage, no output schema, and annotations, the description covers the essential workflow: prerequisites (sync_spread), human interaction requirement, side effects (cannot undo), and behavior for edge cases (windows without pinned lines). An agent can invoke it correctly without additional context.

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%, so both parameters (set and leader) are documented. The description adds context about the leader's role (the window with cursor receives the values) and the default behavior, but this is mostly a restatement of the parameter description. It does not substantially deepen parameter understanding beyond the schema.

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

Purpose5/5

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

The description clearly states the tool's action: inserting each window's pinned value into the field focused in the leading window. It distinguishes itself from sync_spread by focusing on the insertion step and mentioning the prerequisite. The verb 'type' and the resource 'input field' make the purpose unambiguous.

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 provides clear usage context: it must be called after sync_spread, and a person must click into the field first. It implies this is the insertion step, though it does not explicitly contrast with sibling sync tools beyond mentioning sync_spread. The precondition is clearly stated.

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