Skip to main content
Glama
Sign In
Flower MCP

Flower MCP

by Damel91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fow_get_job

Read-onlyIdempotent

Retrieve a durable job's status, result, or failure using its job ID without starting or retrying it. Use it to check read-only progress for scheduled work in a project.

Instructions

Retrieve the status, result or failure of one previously scheduled durable job without starting or retrying it. Single operation; call directly without an operation argument. Prerequisites: Use the durable job ID returned when work was scheduled. Effects: Read-only job status/result/error; polling does not start or retry execution. Exact help (replace operation_name with the selected route): fow_capabilities({"view":"operation","operation_tool":"fow_get_job","operation_name":"call"}).

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": {
      "project_id": "<project_id>",
      "job_id": "<job_id>"
    },
    "name": "fow_get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesDurable job ID returned by the operation that scheduled the work.
project_idYesCanonical lifecycle project ID. Select the existing project explicitly; development Markdown authorities are separate from runtime projects.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.1
    • addedInput schema / properties / job_id / description
      Added value: +"Durable job ID returned by the operation that scheduled the work."
    • addedInput schema / properties / project_id / description
      Added value: +"Canonical lifecycle project ID. Select the existing project explicitly; development Markdown authorities are separate from runtime projects."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond that: polling does not start or retry execution, which is the exact misunderstanding an agent could have for a job-status tool.

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?

Front-loads the core purpose and then labels prerequisites and effects clearly. The trailing fow_capabilities help pointer is useful but adds bulk; still, every sentence carries operational content and none is filler.

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?

With an output schema present, return values need not be spelled out, and the description supplies prerequisites, read-only effects, and a help route. It is complete enough for correct invocation, with the only gap being no explicit tie-break against fow_list_jobs.

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 both job_id and project_id are already documented in the schema, including where the job ID comes from. The description restates the job-ID provenance but adds no format or constraint detail beyond the schema; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Retrieve the status, result or failure of one previously scheduled durable job') and adds a scope boundary ('without starting or retrying it') that distinguishes it from scheduling or list-style siblings like fow_list_jobs. An agent can identify the tool's role without opening the schema.

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?

Gives the prerequisite (use the durable job ID returned when work was scheduled) and clarifies it is a single operation requiring no operation argument. It does not explicitly contrast with the sibling fow_list_jobs, so an agent must infer the one-job-vs-many-jobs split.

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

Deploy Server

Other Tools