Skip to main content
Glama

MatLogica Demo

demo_cancel_job

Destructive

Cancel your queued/running calculation; late worker results cannot be published.

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": {
      "job_id": "<job_id>",
      "guest_session": "<guest_session>"
    },
    "name": "demo_cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
guest_sessionYesWorkspace returned by demo_start_session in this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description earns credit for adding a real, checkable consequence beyond the annotations: worker results that arrive after cancellation cannot be published, which materially affects whether an agent should proceed.

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?

One short sentence, front-loaded with the action and scope, followed by the caveat. No filler and nothing repeated from structured fields.

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

Completeness3/5

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

For a destructive two-parameter call with no output schema and half its parameters undocumented, the definition covers the main risk but leaves gaps: it does not say what the call returns, whether the effect is reversible, or what happens when the job is already complete.

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

Parameters2/5

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

With only 50% schema description coverage, the description would need to compensate, and it says nothing about either parameter. In particular job_id carries only a UUID pattern and no stated meaning, and the description does not explain that the job must still be queued/running for the identifier to be valid.

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 names a specific verb and resource (cancel a calculation job) and narrows scope to 'queued/running', so an agent can tell it apart from a generic job read. It stops short of contrasting itself with the trace-cancel sibling, so the distinction from demo_cancel_trace must be inferred.

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?

The applicable state ('queued/running') is stated, which implies when the call is valid, and the closing clause hints at the consequence of acting on in-flight work. There is no explicit when-not guidance and no routing to alternatives such as demo_cancel_trace or demo_get_job.

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.

Resources