Skip to main content
Glama

fynk MCP

by com.fynk.app
OverviewDiscussionsAdmin

Update document teams

update-document-teams
Destructive

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_actionsYesChanges to apply to the document's team assignments. Teams not mentioned keep their current assignment
document_uuidYesUUID 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

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to open the document in fynk
nameNoName of the document
uuidNoUnique identifier for the document. Do not show to the user unless they ask for it
stageNoWhat stage the document is in currently
teamsNoThe teams the document is assigned to.
_entity_typeNoOnly relevant for tooling. Do not show to the user
document_typeNoIf present, indicates what kind of document this is. Absent when the document has no type assigned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation: it discloses additive semantics (teams not mentioned keep their assignment), idempotency behavior (adding/removing a no-op has no effect), a per-call constraint (each team at most one action), and an account-level constraint (last remaining team cannot be removed).

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?

Front-loads the core action, then uses a scoped bullet list for scenarios followed by tightly packed behavioral notes. Every sentence carries distinct information; no redundancy with the schema.

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?

With annotations covering safety and an output schema handling the return, the description supplies everything else an agent needs: dependency tools, edge-case semantics, and account constraints. 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%, so the baseline is 3, but the description adds a cross-field constraint not present in the schema (each team may appear in at most one action per call) plus the additive override rule. Useful semantics beyond the structured fields.

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?

States a specific verb (adds/removes) on a specific resource (teams on a document), clearly differentiating it from siblings like update-document-tags or update-document-party. An agent can tell exactly what this tool mutates.

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?

Explicitly enumerates the three scenarios (assign, remove, move) and names the dependency tool list-account-teams for discovering valid UUIDs. When-to-use is stated, not inferred.

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

All fynk MCP toolsInspect
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