Skip to main content
Glama

picture_status

Track a Higgsfield picture job: wait up to a set time, return its stage or picture ID when complete, or stop the job.

Instructions

Follow the Higgsfield picture being made (by generate_* or relight): waits up to wait seconds and, when it's done, puts it where that call said and returns the picture id. stop: true stops the job instead. Returns { done: false } with the stage if it's still working, or { job: null } if nothing is being made.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "picture_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopNotrue: stop the picture being made.
waitNoSeconds to wait for it, 0 to 110. Default 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / stop / description
      Added value: +"true: stop the picture being made."
    • addedInput schema / properties / wait / description
      Added value: +"Seconds to wait for it, 0 to 110. Default 50."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the blocking wait behavior, the side effect of placing the finished picture where the originating call specified, and the three return shapes ({done:false}+stage, picture id, {job:null}). It leaves unstated what stop:true returns and whether repeated calls are expected to be made for continued polling, and the placement side effect is described vaguely ('where that call said').

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-loaded with the core verb and resource, then alternative mode, then return shapes. The phrasing 'puts it where that call said' is vague filler where a concrete term would be shorter and clearer, but nothing is extraneous.

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 no output schema, the description correctly takes on return-value explanation and covers the in-progress, success, and idle cases. Gaps remain around the stop:true return value and timeout semantics, but an agent has enough to call it correctly.

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% and both properties carry their own descriptions with the 0-110 range and default. The description adds only a light restatement ('waits up to wait seconds', 'stop: true stops the job instead'), which does not extend meaning beyond the schema, so the 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?

States a specific verb and resource ('Follow the Higgsfield picture being made') and names the producing sibling calls ('generate_* or relight'), which scopes it against status-style siblings. It stops just short of explicitly contrasting with render_status/style_status, so an agent must infer that distinction from the parenthetical.

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?

Clearly frames when to call it: after a generate_*/relight call, to follow progress, and notes that stop:true is the alternative mode for aborting. It gives no explicit 'do not use for renders/styles' exclusion, but the usage context is unambiguous.

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