Skip to main content
Glama
mh-zeynal

gapify-mcp-server

by mh-zeynal

Teams: Update a team

gapify_update_team

Update a support team's name, description, and auto-assignment setting in Gapify. Use it to change team attributes by account and team ID.

Instructions

Update a team's attributes [Teams] PATCH /api/v1/accounts/{account_id}/teams/{team_id} Auth: User API key (header api-access-token). Body fields: name, description, allow_auto_assign. Extra fields can be passed via extra_body. Text values may be written in Persian (Farsi) or any other language and are sent unchanged; IDs, numbers and phone numbers may use Persian or Arabic-Indic digits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe name of the team
team_idYesThe ID of the team to be updated
account_idYesThe numeric ID of the account
extra_bodyNoAdditional JSON body fields to merge into the request (for keys not listed above).
descriptionNoThe description of the team
allow_auto_assignNoIf this setting is turned on, the system would automatically assign the conversation to an agent in the team while assigning the conversation to a team Example: false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds useful context beyond that: the exact HTTP method, required auth header, extra_body merge behavior, and the handling of Persian/Arabic-Indic digits and unchanged text values.

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?

The description is front-loaded with the core action and then efficiently supplies endpoint, auth, body, extra_body, and input-language details. Every sentence carries relevant information for correct invocation, with no filler.

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

Completeness4/5

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

Given full schema coverage, annotations covering safety/idempotency, and no output schema, the description is nearly complete. It covers auth, endpoint, writable fields, extra_body, and parameter-language handling, though it does not explicitly state partial-update semantics or behavior for omitted fields.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by naming the primary writable body fields, explaining extra_body for unlisted fields, and noting that text values and numeric IDs may use Persian or Arabic-Indic digits without transformation.

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 states a specific verb and resource ('Update a team's attributes'), includes the endpoint, and clearly distinguishes this from sibling team tools like create/get/delete and team-agent operations. An agent can identify this as the tool for changing team-level metadata.

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

Usage Guidelines3/5

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

The description implies usage through 'Update' and lists the updatable body fields, but it does not explicitly say when to use this tool versus alternatives such as gapify_update_team_agents or gapify_create_team. No exclusions or prerequisites beyond the auth header are provided.

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