Skip to main content
Glama

modify_assignment

Modify an existing assignment group by replacing its definition and all time slots. Use new parameters for title, users, dates, and times via group ID.

Instructions

Modify an existing assignment group with human-friendly parameters.

Replaces the group definition and all its time slots. The server marks a tombstone for the old group, removes old slots, and creates new ones. Uses the same parameter format as create_assignment but requires group_id.

Args: id_activity: Activity ID group_id: Existing group ID to update (from get_activity or create_assignment result) user_ids: List of user IDs to assign titre: Assignment title start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format (same as start_date for single-day) start_hour: Start hour 0-23 start_minute: Start minute 0-59 end_hour: End hour 0-23 end_minute: End minute 0-59 weekdays: Active weekday names for recursive mode. Omit for single-day. notes: Optional notes text

Returns: JSON string — human-readable summary with updated slot details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
titreYes
end_dateYes
end_hourYes
group_idYes
user_idsYes
weekdaysNo
end_minuteYes
start_dateYes
start_hourYes
id_activityYes
start_minuteYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses internal behavior: 'marks a tombstone for the old group, removes old slots, and creates new ones.' This gives clear insight into destructive, replacement nature.

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?

Well-structured with explicit purpose, behavioral note, parameter list, and return value. Slightly verbose due to full parameter list, but still efficient and readable.

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?

Covers purpose, behavior, all parameters, and return type. Output schema exists, so return explanation is sufficient. Missing error scenarios or prerequisites (e.g., permissions), but adequate for a complex tool.

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

Parameters5/5

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

Schema has 0% description coverage, but the description includes an Args block that explains all 12 parameters with clear descriptions, fully compensating for the schema gap.

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?

Clearly states 'Modify an existing assignment group' with a specific verb and resource. Notes similarity to create_assignment, but does not explicitly differentiate from sibling update_assignment, leaving some ambiguity.

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?

Provides context that it replaces the entire group definition and time slots, implying full updates. Mentions parameter format similarity to create_assignment, but lacks explicit when-to-use or when-not-to-use guidance and does not compare to update_assignment.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sebastien-VZN/axomind-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server