Skip to main content
Glama

Get a strategy campaign

get_planner_campaign
Read-onlyIdempotent

One 12-stage plan with stage statuses and a quality summary. Use get_planner_stage for a stage artifact and get_planner_quality for the gate verdict.

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_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful return-shape context (12 stages, statuses, quality summary), which matters since there is no output schema. It says nothing about behavior on an unknown campaign_id or whether stage statuses are live or snapshotted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the return content front-loaded before the sibling routing. Every clause earns its place.

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?

For a simple read tool with annotations covering safety and no output schema, the description supplies the return shape and the alternatives. The only real gap is the meaning/format of campaign_id and error behavior for a missing campaign.

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 one parameter, campaign_id, with 0% schema description coverage, so the description carries the burden and does not explain it. The phrase 'One 12-stage plan' implies a single campaign is selected per call, which is mild compensation. Adequate but not compensating for the coverage gap.

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 the resource and its shape concretely: 'One 12-stage plan with stage statuses and a quality summary.' That tells an agent exactly what comes back, which is more than a bare verb+resource. It stops short of an explicit retrieval verb, but the scope is unambiguous.

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?

It routes the agent explicitly: 'Use get_planner_stage for a stage artifact and get_planner_quality for the gate verdict.' That is clear when-to-use-elsewhere guidance. It does not state when *not* to use this tool (e.g. listing campaigns vs. fetching one), so it falls short of a 5.

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