Skip to main content
Glama

Get the quality gate

get_planner_quality
Read-onlyIdempotent

The blocking quality gate for a strategy campaign: passed, score, launch recommendation and violations. A campaign is not launch-ready unless passed is true; this tool never approves it.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_planner_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Read-only and idempotent behavior are already in annotations, and the description adds genuinely new context: the gate is 'blocking' and the tool never grants approval, so an agent cannot mistake a passing result for a launch action. It says nothing about behavior for an unknown or non-existent campaign_id, which would be the remaining useful detail.

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?

Two short sentences, with what the tool returns front-loaded and the readiness rule immediately after. The opening is a noun phrase rather than a verb phrase, but no sentence 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 no output schema, the description usefully lists the four returned fields, and annotations already carry the safety profile. The only gap is that the sole input parameter is unexplained, which is minor for a single required identifier.

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?

The schema gives campaign_id no description at all (0% coverage), so the description must compensate, and it does not mention the parameter or its accepted format. The name campaign_id is self-explanatory for this API family, which keeps this at a minimum-viable 3 rather than lower.

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 names a specific resource (the blocking quality gate for a strategy campaign) and enumerates exactly what it returns: passed, score, launch recommendation and violations. It is clearly a read of a derived quality artifact rather than a campaign record, setting it apart from get_planner_campaign or get_planner_stage, though it does not name those siblings explicitly.

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?

'A campaign is not launch-ready unless passed is true' gives the decision context in which this tool is consulted, and 'this tool never approves it' draws a when-not boundary. It stops short of naming the alternative call an agent should make when it actually wants to launch or approve, so no full routing guidance.

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