Skip to main content
Glama
Sign In

Scribase

by com.scribase
OverviewDiscussionsAdmin

Pause, resume or reschedule

schedule.update

Change a job: active false pauses it, true resumes it; schedule sets a new timer. 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.update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe job name
activeNofalse pauses, true resumes
branchNoBranch (environment) id. Optional: defaults to `production`.
scheduleNoFive cron fields in UTC, or "N seconds"
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

A3.8/5.0
Behavior4/5

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

The annotations already disclose that this is a non-readonly, non-idempotent, non-destructive mutation, and the description adds useful behavioral context by stating the required scope, 'database:write.' It also clarifies that `active` false pauses, true resumes, and `schedule` sets a new timer, though it does not describe side effects or whether changes are immediate. No contradiction with annotations is present.

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?

The description is a single compact sentence that front-loads the core action and follows with the key parameter meanings and scope. Every clause carries useful information, and there is no unnecessary wording.

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 six-parameter update tool with full schema coverage and clear annotations, the description covers the main purpose, key field effects, and required scope. It leaves out explicit routing to sibling schedule tools, but the core information needed to select and invoke the tool is present.

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 all six parameters, including defaults and the cron/seconds format for `schedule`. The description restates the `active` and `schedule` semantics but adds no syntax, edge-case, or defaulting detail beyond what the schema provides, so the 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 gives a specific verb and resource: 'Change a job,' and then explains the two main modifications, pausing/resuming via `active` and rescheduling via `schedule`. It implies this is an update operation rather than create/delete/run, but it does not explicitly name or differentiate from sibling tools such as schedule.create, schedule.delete, or schedule.run.

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?

Usage is implied by the title 'Pause, resume or reschedule' and by 'Change a job,' which suggests this tool is for modifying an existing schedule. However, there is no explicit guidance on when to use this instead of schedule.create, schedule.delete, schedule.run, or schedule.list, and no prerequisites are stated.

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