Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

Delete a schedule

schedule.delete
Destructive

Delete a job and stop its runs. Show the user which job goes, then call with confirm: true. Scope: database:write.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "schedule.delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe job name
branchNoBranch (environment) id. Optional: defaults to `production`.
confirmNoMust be true to run a destructive operation, after the user approved it
project_idNoProject id. Optional: defaults to the project created or used last in this session, or the only one.
organization_idNoOrganization id. Optional: defaults to the token's organization, or the only one you belong to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new behavior: the deletion also halts the job's runs, the call requires explicit confirm: true after user approval, and it needs the database:write scope. It does not state whether the deletion is recoverable, which would complete the picture.

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?

Three short sentences with the action and its side effect first, the approval/confirm procedure second, and the scope last. No filler and no repetition of schema content.

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?

For a five-parameter destructive tool with no output schema, the description covers the essential agent-facing facts: what is removed, what else stops, and the confirmation gate. The main omission is reversibility and any dependency behavior for jobs tied to the deleted schedule.

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 the schema already documents all five parameters including confirm's requirement and the defaulting rules for branch, project_id, and organization_id. The description reinforces the confirm gate but adds no new syntax or semantics beyond what the schema states. Baseline 3 applies.

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?

"Delete a job and stop its runs" gives a specific verb plus resource and names the side effect, which separates it from schedule.create, schedule.update, and schedule.run in the sibling list. It stops short of explicitly contrasting with the nearest alternative (e.g., disabling via schedule.update), so it is clear but not maximally differentiated.

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

Usage Guidelines4/5

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

It prescribes a concrete pre-call workflow: show the user which job will be removed, then invoke with confirm: true. That is real when-to-use guidance for a destructive action. It does not say when to prefer an alternative over deletion, so it falls short of full alternative routing.

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

All Scribase toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources