Skip to main content
Glama

platform_trigger

Triggers an immediate platform run for a registered, enabled source while enforcing single-flight guardrails; returns a pending run ID or a clear refusal.

Instructions

Trigger an immediate platform run for source (insert pending_runs).

Same validation and guardrails as the panel's trigger button: the source must be registered in crawl_sources and enabled, and single- flight applies (refused while an open run exists). Returns {"status": "triggered", "pending_id": ...} or a clear refusal text.

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": {
      "source": "<source>"
    },
    "name": "platform_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNooptional run param override recorded on the pending row (passed through to the dispatcher inside params).
sourceYessource name as registered in crawl_sources.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, and the description usefully adds the write target (pending_runs), the validation/guardrail model, the single-flight refusal, and the success/refusal response shape. It stops short of saying whether the run executes asynchronously after the pending row is created or how refusals are surfaced to the caller.

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 action and its side effect are front-loaded in the first sentence, with constraints and return values following in a compact block. Some of the return-value detail is redundant given the output schema, but nothing is padded or unclear.

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 two-parameter mutation with full annotation coverage and an output schema, the description covers preconditions, side effects, and refusal behavior adequately. The main residual gap is asynchrony/dispatch timing, which an agent would want before polling for results.

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 both parameters are already documented, including limit's pass-through behavior. The description only reinforces that source must be a registered, enabled crawl_sources entry; it says nothing about limit itself, so it adds marginal meaning over the schema — the baseline 3.

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 states a specific verb and resource ('Trigger an immediate platform run for source') plus the concrete side effect ('insert pending_runs'), which is far more informative than the bare name. It does not, however, distinguish itself from look-alike siblings such as policy_trigger_now or explain its relationship to platform_sources/platform_runs.

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 gives clear preconditions for use: the source must be registered in crawl_sources and enabled, and single-flight means the call is refused while an open run exists. What is missing is routing guidance — no statement of when to prefer this over policy_trigger_now or how to find a valid source name.

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