Skip to main content
Glama
Teamwork

Teamwork

Official
by Teamwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

twprojects-update_jobrole

Update a job role's name by providing its unique ID, ensuring team role data stays current.

Instructions

Update job role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the job role to update.
nameNoThe name of the job role.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.39.3
    • removedInput schema / properties / name / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / name / type
      Added value: +"string"
  2. Addedv1.18.3
  3. Removedv1.18.2
  4. Addedv1.17.2

TDQS

C2.9/5.0
Behavior2/5

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

The description simply restates the mutation and adds no behavioral context beyond what annotations already convey (readOnlyHint=false, destructiveHint=false). It does not disclose partial-update semantics, permission needs, or effects beyond the fact of updating.

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 a single, short sentence with no wasted words. It is front-loaded and appropriately sized for a simple two-parameter update tool, though it is too bare to add much value.

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?

Given the low complexity, full schema coverage, and annotations, this is a minimally viable description. It is missing any note about optional fields or expected usage context, but an agent can likely operate it correctly with the schema alone.

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 description coverage is 100%, so the schema already documents id and name. The description adds no further meaning about how these parameters behave, but the baseline is acceptable because the schema carries the burden.

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 states a clear verb and resource ('Update job role'), so an agent can tell this is the mutation counterpart to get_jobrole and list_jobroles. It lacks any scope or effect details, but the core purpose is unambiguous.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus other update_* tools or when updating a job role is appropriate. The description only states the action and leaves all usage decisions to inference.

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