Skip to main content
Glama

Check a campaign is ready to launch

check_campaign_readiness
Read-only

Use this before launching a campaign, to see whether it would start now and, if not, the reason. Also counts the people on its lists: those with a work email, those without one, and those with a LinkedIn profile. Nothing changes and nothing is sent. Free.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "check_campaign_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is partly given. The description adds value beyond that by stating explicitly that nothing changes and nothing is sent, that a failure returns the reason, that counts are computed over the campaign's lists, and that the call is free (a cost/credit signal not present in annotations).

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?

Three short sentences, front-loaded with the primary purpose and the pre-launch trigger. Every sentence earns its place; the only slight looseness is the terse 'Free.' fragment appended at the end.

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 carries the burden of explaining return values, and it does: readiness verdict, blocking reason, and three population counts. For a one-parameter read-only tool this is close to sufficient, though it does not describe result shape or edge cases such as an empty list.

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?

There is a single parameter (campaignId) with 100% schema description coverage, so the schema already carries the full parameter meaning. The description adds nothing about id format, scope, or lookup behavior. Baseline 3 applies when the schema does all the work.

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-plus-resource: check whether a campaign would start now, return the blocking reason, and count list members by work email / no work email / LinkedIn profile. This is clearly distinguishable from launch_campaign, which the phrase 'before launching a campaign' implicitly contrasts. It stops short of naming the sibling tool outright.

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?

'Use this before launching a campaign' gives a clear temporal trigger and an implied pairing with launch_campaign. There is no explicit when-not, but the read-only, zero-side-effect framing ('Nothing changes and nothing is sent') makes the boundary obvious to an agent.

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