Skip to main content
Glama

generate_battlecard

Builds a ready-to-ship Markdown commercial battlecard from seed App Store keywords, combining opportunity scoring, deduplicated pricing, clustered 1–3★ quotes, buyout anchors, and ASO hooks.

Instructions

[PRO] Generate a ready-to-ship Markdown Commercial Battlecard: Opportunity Score (0-100), deduplicated pricing table, clustered 1-3★ verbatim quotes, anti-subscription buyout anchor, and ASO hooks. Requires OPC1. license.

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": {
      "keywords": "<keywords>"
    },
    "name": "generate_battlecard"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNo2-letter App Store storefront codeus
keywordsYesSeed keywords for the target App Store niche
license_keyNoOptional inline OPC1.<payload>.<sig> Pro license token
use_fixtureNoUse deterministic offline fixture dataset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the Markdown output format, the generated sections, and a Pro license requirement, but it omits whether the tool is read-only, how license failures are handled, rate/cost behavior, and the meaning of the fixture mode.

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?

The description is front-loaded with the action and output artifact, and every clause describes a substantive part of the result. It is dense but not padded, though the single long sentence is slightly crammed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description supplies a useful inventory of return components and the license prerequisite. However, it leaves meaningful gaps around usage selection, error/license behavior, fixture semantics, and response structure details.

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?

Schema description coverage is 100%, so the schema already documents the four parameters. The description mentions seed keywords only indirectly through the domain context and otherwise adds no parameter meaning beyond the schema defaults and formats.

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 gives a specific verb and resource: 'Generate a ... Markdown Commercial Battlecard', and it enumerates the card's contents. It is clearly distinguishable in substance from compare_matrix and probe_keyword, but it does not explicitly differentiate itself from those siblings.

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

Usage Guidelines2/5

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

The description implies this is for commercial battlecards and notes a Pro license requirement, but it does not state when an agent should choose this tool over alternatives. No sibling or alternative workflow is named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools