Skip to main content
Glama

Create Contract Event

create-contract-event

[Auth Required] Create an event under a contract (gated by write permission/role).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd datetime (Y-m-d H:i:s or ISO8601; optional for schedule-less tasks)
dataNoFree-form metadata object (default {})
dateNoEvent date (YYYY-MM-DD)
filesNoAttached user_files ids (multiple). Use /api/agent/upload first to get ids. Markdown inline images: ![](url) where url comes from event.files[].url in the payload.
labelYesEvent label
startNoStart datetime (Y-m-d H:i:s or ISO8601; optional for schedule-less tasks)
usersNoNon-benefitable participants with their event roles. Each: {participable_id: int, type: 'user'|'agent', role_id: int}. Reviewer=5, QA=6. All must be contract members.
amountNoAmount in minor units
type_idNoEvent type id (1=ForSale, 2=Busy, 3=Paid, 4=NotForSale; default 2=Busy for contract-tasks)
currencyNoCurrency code
durationNoDuration in minutes
settingsNoFree-form settings blob (tags + event-to-event relations).
timezoneNoIANA timezone (default UTC)
status_idNoEvent status id (100=Pending, 200=Approved, 222=Done, 300=InTesting, 350=InReview, 400=Confirmed, 499=Closed, 555=Canceled, 777=Declined; default 100=Pending)
benefitableNoAssignee of the event. {type: 'user'|'agent', value: int}. Must be a contract member.
contract_idYesContract ID
descriptionNoEvent description
kal_schedule_idNoSchedule ID (optional; auto-resolved from benefitable=user ContractHand when omitted; contract-tasks may be schedule-less)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations are empty, so description should disclose behavioral traits. It only says it creates an event and requires auth. No mention of side effects, return data, constraints, or effects on related resources. For a complex tool with 18 parameters, this is insufficient.

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 sentence that conveys the core purpose and a constraint. It is efficient, though it may be too terse for a complex tool.

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

Completeness2/5

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

With 18 parameters, no output schema, and empty annotations, the description should provide broader context. It lacks details on what an event is, how to structure requests, error handling, and return values. Incomplete for a tool of this complexity.

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 coverage is 100%, so each parameter is documented. The description adds no additional parameter meaning beyond what is in the schema. Baseline 3 is appropriate.

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 clearly states the verb 'Create' and the resource 'event under a contract', and mentions the auth requirement. It distinguishes from read tools but does not differentiate from similar creation tools like 'book-event'.

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 on when to use this tool versus alternatives (e.g., book-event). Only mentions auth requirement, but no context on typical use cases or preconditions beyond permissions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.