fynk MCP

Update document teams

update-document-teams

DestructiveIdempotent

Adds teams to and/or removes teams from a document.

Use this tool when:

A document should be assigned to one or more teams
A team assignment should be removed from a document
A document should be moved from one team to another (one remove and one add action)

Actions are applied on top of the document's current team assignments: teams not mentioned in team_actions keep their assignment. Each team may appear in at most one action per call. Adding an already-assigned team or removing a team that is not assigned has no effect. Use the list-account-teams tool to discover valid team UUIDs. Some accounts enforce team assignment, in which case the last remaining team cannot be removed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "document_uuid": "<document_uuid>",
      "team_actions": "<team_actions>"
    },
    "name": "update-document-teams"
  }
}

Input Schema

Name	Required	Description	Default
`team_actions`	Yes	Changes to apply to the document's team assignments. Teams not mentioned keep their current assignment
`document_uuid`	Yes	UUID of the document whose teams to update. If you don't already have the document's UUID, use the list-documents tool to find it.

Output Schema

Name	Required	Description
`url`	No	URL to open the document in fynk
`name`	No	Name of the document
`uuid`	No	Unique identifier for the document. Do not show to the user unless they ask for it
`stage`	No	What stage the document is in currently
`teams`	No	The teams the document is assigned to.
`_entity_type`	No	Only relevant for tooling. Do not show to the user
`document_type`	No	If present, indicates what kind of document this is. Absent when the document has no type assigned

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=true) by explaining merge semantics: unmentioned teams keep their assignment, one action per team per call, and add/remove on a wrong-state team is a no-op. It also discloses the account-level constraint that the last remaining team cannot be removed when enforcement is on — key risk information for a mutation.

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?

Front-loaded one-line summary followed by scannable bullets, then behavioral notes. Every sentence carries useful information, though the when-to-use bullet list slightly restates the opening sentence.

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?

A destructive mutation with 2 required params and an output schema; the description covers semantics, no-op edge cases, prerequisites for discovering UUIDs, and the account enforcement constraint. Nothing material is missing.

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

Parameters4/5

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

Schema coverage is 100% and the schema already documents the team_actions items and UUID lookups, so baseline is 3. The description adds real semantics on top: the patch/merge model of team_actions and the rule that each team may appear in at most one action per call.

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?

Opens with a specific verb and resource ('Adds teams to and/or removes teams from a document') and immediately distinguishes this team-assignment operation from siblings such as update-account-team (edits a team itself) and attach-account-users-to-team (manages members). An agent can pick this tool without inspecting the schema.

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

Usage Guidelines5/5

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

An explicit bulleted when-to-use list covers assignment, unassignment, and the composite move case (one remove + one add). It also routes the agent to list-account-teams for valid UUIDs and list-documents for document UUIDs.

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

All fynk MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?