Skip to main content
Glama

Server Details

Free bar for digital product briefs: your model judges, open rules and code score it.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
welance/perfect-brief
GitHub Stars
1
ChatGPT
–
Claude
brief bar_

TDQS

A4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct role in a linear pipeline: read rules, get template, run deterministic checks, get the judge prompt, aggregate verdicts, and get an improvement prompt. The descriptions explicitly delimit boundaries (e.g., check_brief says 'never a score', aggregate_verdicts says it produces the score), so an agent can select correctly without guessing.

Naming Consistency4/5

Names are uniformly snake_case, and four of seven use the get_* verb_noun pattern (get_rules, get_brief_template, get_judge_prompt, get_improvement_prompt), with aggregate_verdicts and check_brief following verb_noun too. bar_status is a noun-style outlier that slightly breaks the pattern.

Tool Count5/5

Seven tools map cleanly onto one evaluation workflow with no filler; each earns its place and the surface stays small enough to reason about. Nothing feels padded or missing at the count level.

Completeness4/5

The lifecycle is well covered: rules, template, pre-flight check, judge prompt, aggregation, and improvement prompt form an end-to-end loop. The only gap is that there is no tool to retrieve the official directory score or prior evaluations, which is arguably deliberate given the advisory-only design.

Available Tools

7 tools
aggregate_verdictsScore from your verdictsA
Read-onlyIdempotent
Inspect

Turn your model's verdicts into the bar's score, gate and decision. Advisory.

Validates the verdicts against the live ruleset (every rule exactly once,
valid status and confidence, the version you judged at) and against the
brief (each quote must be copied verbatim), then aggregates them with the
same engine that scores on the service: same verdicts, same number.
Any error means no score — fix and resend.

The result is tagged evaluation_source "client" and authoritative false:
your model wrote the verdicts, so it is advice, never a welance score, and
it cannot authorise publication on the welance/directory (the directory
scores every brief itself). Say so when you report it. Fix gate.missing
first. directory_context false drops the directory-only policy rules.

Inputs: brief (required), verdicts (required), ruleset_version (required), directory_context.

bar_statusBar statusA
Read-onlyIdempotent
Inspect

Which ruleset version is live, and what this free surface can do.

Confirms the mode (bring your own model, zero provider calls, no fallback to welance's model) and the tools available.

Inputs: no named parameters.

check_briefRun deterministic checksA
Read-onlyIdempotent
Inspect

Deterministic checks only — semantic coverage is INCOMPLETE. Never a score.

Finds what a pattern can find for certain: emails, URLs and phone numbers
(which block anonymisation), a stated budget and timeline, personal-data
cues without a compliance cue, unfilled placeholders, the title line and
labelled sections. It does not judge meaning: company or person names, a
vague problem or an unmeasurable goal pass straight through. Use it as a
quick pre-flight, then judge with get_judge_prompt and aggregate_verdicts.

Inputs: brief (required), directory_context.

get_brief_templateGet a brief templateA
Read-onlyIdempotent
Inspect

A brief template built from the live rules, with the inputs each section needs.

Use it to start a brief from nothing, or to see which section a gap belongs in. Markdown, one section per rule, gate rules marked; write in any language.

Inputs: no named parameters.

get_improvement_promptGet an improvement promptB
Read-onlyIdempotent
Inspect

A working order for improving a brief with your own model, gate first.

Pass the verdicts you already have (the JSON array from your model) to
target the failing rules in weight order; without them the prompt walks
every rule. The prompt keeps the author's voice and forbids invented
scores and facts. Nothing is generated here: your model does the writing.

Inputs: brief (required), verdicts, directory_context.

get_judge_promptGet the judge promptA
Read-onlyIdempotent
Inspect

The judge prompt and verdict JSON Schema, for YOUR model to answer. Free.

This is the service judge's own prompt, word for word, so your model grades
against the same bar. Pass the brief to get it embedded, or leave it empty
for a template with a {{BRIEF}} placeholder. Answer the prompt with your
own model (temperature 0 if you can), return only the JSON array it asks
for, and send that array with the brief and the returned ruleset_version to
aggregate_verdicts. welance runs no model for this.

Inputs: brief.

get_rulesRead the brief rulesA
Read-onlyIdempotent
Inspect

Read the bar before judging anything. Free; no model runs.

Returns the live catalogue with its version: every rule's id, title,
criteria (what the judge reads), weight, gate role, policy context and how
to pass it, plus the arithmetic — status scores, confidence threshold,
accept threshold, bands, the gate and which policy contexts can be turned
off. The number of rules is whatever the live catalogue says.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.