Skip to main content
Glama
127,427 tools. Last updated 2026-05-05 16:38

"A task management app for scheduling appointments" matching MCP tools:

  • Task management operations. Create and manage task lists and individual tasks within workspaces and shares. Tasks support statuses, priorities, assignees, dependencies, and bulk operations. Responses include `created_by` (user ID of creator). On shares, requires admin or named member role. Destructive actions: delete-list soft-deletes a task list and all its tasks, delete-task soft-deletes a task. Actions & required params: - list-lists: profile_type, profile_id (+ optional: sort_by, sort_dir, limit, offset, format) - create-list: profile_type, profile_id, name (+ optional: description) - list-details: list_id (+ optional: format) - update-list: list_id (+ optional: name, description) - delete-list: list_id [DESTRUCTIVE] - list-tasks: list_id (+ optional: sort_by, sort_dir, status, assignee, limit, offset, format) - create-task: list_id, title (+ optional: description, status, priority, assignee_id, dependencies, node_id) - task-details: list_id, task_id (+ optional: format) - update-task: list_id, task_id (+ optional: title, description, status, priority, assignee_id, dependencies, node_id) - delete-task: list_id, task_id [DESTRUCTIVE] - change-status: list_id, task_id, status - assign-task: list_id, task_id (+ optional: assignee_id) - bulk-status: list_id, task_ids, status - move-task: list_id, task_id, target_task_list_id — move a task to a different list (+ optional: sort_order) - reorder-tasks: list_id, task_ids — reorder tasks within a list - reorder-lists: profile_type, profile_id, list_ids — reorder task lists - filtered-list: profile_type, profile_id, filter (+ optional: status [required when filter=status], limit, offset, format) - summary: profile_type, profile_id (+ optional: format)
    Connector
  • Check submissions for a task you published. Use this to see if a human has submitted evidence for your task. You can then use em_approve_submission to accept or reject. Args: params (CheckSubmissionInput): Validated input parameters containing: - task_id (str): UUID of the task - agent_id (str): Your agent ID (for authorization) - response_format (ResponseFormat): markdown or json Returns: str: Submission details or "No submissions yet".
    Connector
  • Apply to work on a published task. Workers can browse available tasks and apply to work on them. The agent who published the task will review applications and assign the task to a chosen worker. Requirements: - Worker must be registered in the system - Task must be in 'published' status - Worker must meet minimum reputation requirements - Worker cannot have already applied to this task Args: params (ApplyToTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to apply for - executor_id (str): Your executor ID - message (str): Optional message to the agent explaining qualifications Returns: str: Confirmation of application or error message. Status Flow: Task remains 'published' until agent assigns it. Worker's application goes into 'pending' status.
    Connector
  • Submit completed work with evidence for an assigned task. After completing a task, use this to submit your evidence for review. The agent will verify your submission and release payment if approved. Requirements: - You must be assigned to this task - Task must be in 'accepted' or 'in_progress' status - Evidence must match the task's evidence_schema - All required evidence fields must be provided Args: params (SubmitWorkInput): Validated input parameters containing: - task_id (str): UUID of the task - executor_id (str): Your executor ID - evidence (dict): Evidence matching the task's requirements - notes (str): Optional notes about the submission Returns: str: Confirmation of submission or error message. Status Flow: accepted/in_progress -> submitted -> verifying -> completed Evidence Format Examples: Photo task: {"photo": "ipfs://Qm...", "gps": {"lat": 25.76, "lng": -80.19}} Document task: {"document": "https://storage.../doc.pdf", "timestamp": "2026-01-25T10:30:00Z"} Observation task: {"text_response": "Store is open, 5 people in line", "photo": "ipfs://..."}
    Connector
  • Find people who hold or have held officer positions (director, secretary, member, partner) at companies registered in a jurisdiction, by name. Returns a list of officer candidates each with an officer_id, name, and (where the registry exposes it) the number of appointments held. Use the officer_id in get_officer_appointments to retrieve every company that person has been appointed to. This is the entry point for 'follow the human, not the company' investigations.
    Connector
  • Apply to work on a published task. Workers can browse available tasks and apply to work on them. The agent who published the task will review applications and assign the task to a chosen worker. Requirements: - Worker must be registered in the system - Task must be in 'published' status - Worker must meet minimum reputation requirements - Worker cannot have already applied to this task Args: params (ApplyToTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to apply for - executor_id (str): Your executor ID - message (str): Optional message to the agent explaining qualifications Returns: str: Confirmation of application or error message. Status Flow: Task remains 'published' until agent assigns it. Worker's application goes into 'pending' status.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Discover the best AXIS workflow for a purchasing or compliance task. Free, no auth, and logs lightweight task metadata for intent analytics. Example: task_description='prepare for autonomous Visa checkout'. Use this when you need commerce-specific triage and next-step guidance. Use search_and_discover_tools instead for non-commerce keyword routing across all programs.
    Connector
  • Retrieves details of a specific task instance from a Cloud Composer environment. Use this tool to retrieve details of a specific task instance - such as its state, start time, end time, or parameters - to understand its status or to debug a failure. This tool does not return task instance logs directly. Instead, use the `cloud_logging_filter` field from the response to query Cloud Logging for the logs for this task instance.
    Connector
  • Get the current escrow payment status for a task. Returns the payment state including: - Authorization status - Amount locked, released, and refunded - Transaction hashes - Current payment strategy Args: params: task_id Returns: Payment status details or "not found" if task has no escrow.
    Connector
  • Creates a tester group for a Release Management connected app. Tester groups can be used to distribute installable artifacts to testers automatically. When a new installable artifact is available, the tester groups can either automatically or manually be notified via email. The notification email will contain a link to the installable artifact page for the artifact within Bitrise Release Management. A Release Management connected app can have multiple tester groups. Project team members of the connected app can be selected to be testers and added to the tester group. This endpoint has an elevated access level requirement. Only the owner of the related Bitrise Workspace, a workspace manager or the related project's admin can manage tester groups.
    Connector
  • Returns Argentine national public holidays for any given year. Use this tool when calculating delivery dates, scheduling appointments, computing working days, or any task requiring knowledge of non-working days in Argentina. Returns all national holidays with dates in YYYY-MM-DD format and names in both Spanish and English. Note: Argentina also has bridge holidays (feriados puente) declared annually by the government which are not included here.
    Connector
  • Retrieve events from a specific calendar within a time range. Use this to view scheduled events, check availability, or find specific appointments. Times are interpreted in the provided timezone. Without dateMax, returns all future events from dateMin. IMPORTANT: For single day events, use next day as dateMax (e.g., dateMin='2024-01-15' and dateMax='2024-01-16'). Event IDs from this tool are required for update/delete operations.
    Connector
  • Returns Mexican national public holidays for any given year. Use this tool when calculating delivery dates, scheduling appointments, or any task requiring knowledge of non-working days in Mexico. Returns all national holidays with dates in YYYY-MM-DD format and names in both Spanish and English. Note: some Mexican holidays fall on the nearest Monday (puente) — the dates returned are the fixed calendar dates as established by law.
    Connector
  • Generate a use case for a given topic or goal. The process: 1) search 60,000+ AI skills by keyword, 2) AI-score top results for relevance, 3) select best 5 skills for the task, 4) generate structured use case with skill recommendations. Use when a user describes a task and wants a curated AI skill stack.
    Connector
  • Delete a calendar and all its appointments. Requires full scope. This action is irreversible.
    Connector
  • Cancel a task you published (only if still in 'published' or 'accepted' status). Use this if you no longer need the task completed. Args: params (CancelTaskInput): Validated input parameters containing: - task_id (str): UUID of the task to cancel - agent_id (str): Your agent ID (for authorization) - reason (str): Reason for cancellation Returns: str: Confirmation of cancellation.
    Connector
  • ESCROW FLOW ONLY. For direct-settlement tasks (settlementMode='direct') use acknowledge_direct_settlement_task instead — this endpoint returns 400 with a pointer when called on a direct task. Approve a completed task after reviewing the proof. Triggers payout to the operator. The task must be in UnderReview status AND settlementMode='escrow'. Funds move from locked to earned. Requires authentication.
    Connector
  • List every deployed API function for a project: route, method, runtime tier, type ('scheduled' if the function has at least one active scheduled task, else 'api'), and 24-hour invocation and error counts. This is the 'what routes did I ship' introspection tool. Call it after a fork, after picking up an unfamiliar project, or to verify a deploy registered the endpoints you expected. Much cheaper than reading every api/ file with read_file. For scheduling details (cron, fire_at, payload, run history) use list_cron_jobs.
    Connector