Skip to main content
Glama

Retrieve a Slow brand_guideline_specify Generation's Result

brand_guideline_status
Read-onlyIdempotent

Resolves a brand_job_ref returned by brand_guideline_specify when its race-to-complete window elapsed before generation finished. Read-only, in-process lookup; it does not re-run generation. Returns {"status": "processing"} if still running, {"status": "complete", "brand_ref": ..., "project_id": ..., "recommended_candidate_id": ..., "candidate_count": ...} once done (a compact summary -- use the returned brand_ref with brand_guideline_select/brand_guideline_pdf/brand_guideline_claims for full detail, the same pattern every other Brand Standard tool already uses), or {"status": "failed", "error_code": ..., "message": ...} if generation genuinely failed server-side. An unknown or expired brand_job_ref returns a structured BRAND_JOB_NOT_FOUND error, never a crash or empty success.

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": {
      "brand_job_ref": "<brand_job_ref>"
    },
    "name": "brand_guideline_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_job_refYesThe brand_job_ref returned by brand_guideline_specify's processing response.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the safety profile is covered; the description adds real context beyond that: in-process lookup semantics, no re-execution of generation, and the three terminal states (processing, complete, failed). The error behavior is also disclosed concretely — an unknown or expired ref yields a structured BRAND_JOB_NOT_FOUND rather than a crash or empty success — which is exactly the kind of edge case an agent needs before calling.

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 trigger and scope, and each clause carries information about a distinct outcome. It is dense but the long parenthetical about following up with other tools is slightly heavy for a single sentence; trimming it to one short clause would lose nothing.

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?

Complete for a single-parameter polling tool: the description covers trigger, non-rerun semantics, all response branches, and the error case, even though an output schema exists and would have carried the response shape. Nothing essential for a correct call is missing.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents brand_job_ref. The description restates its provenance ('returned by brand_guideline_specify') and adds the enum-like valid values only for the response, not the input, so it contributes little meaning 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 ('Resolves a brand_job_ref') and pins it to a precise lifecycle moment: a job created by brand_guideline_specify whose race-to-complete window elapsed. That framing makes it unmistakable versus brand_guideline_specify (starts generation) and the select/pdf/claims tools (consume results).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trigger condition is explicit ('when its race-to-complete window elapsed before generation finished') and it rules out a misuse case by stating 'it does not re-run generation.' It also routes the agent onward, telling it to use brand_ref with brand_guideline_select/brand_guideline_pdf/brand_guideline_claims for full detail rather than expecting that content here.

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