Skip to main content
Glama

The Marketing Vault

Stress-test an idea

stress_test_idea

Reviews ideas through expert perspectives, debate, market research or a concise core answer. Output is saved to the Library and uses one generation. Nothing is sent or published.

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": {
      "template": "<template>",
      "details": "<details>"
    },
    "name": "stress_test_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentNoContent for the selected template.
detailsYesWhat the user wants, including supplied source text, goals or constraints.
templateYesbusiness-experts: Review an idea through business expert perspectives. debate-challenge: Debate and challenge a proposed strategy. market-research-test: Stress-test an idea against a market research group. core-answer: Distill a strategic question to its core answer.
business_nameNoBusiness name for the selected template.
proposed_strategyNoProposed strategy for the selected template.
business_profile_idNoBusiness profile id. Required when the account has multiple Businesses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=false; the description usefully explains that consequence – output is saved to the Library (the internal write) and nothing is sent or published (no external effect). It also discloses the cost model ("uses one generation"), which is real operational context an agent would not otherwise have. It stops short of describing what the saved Library artifact looks like or how to retrieve it.

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 sentences, no filler, with the capability stated first and the side effects second. The mode enumeration in the opening sentence is slightly list-like but each clause carries information an agent needs.

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 six params at full schema coverage, two required, and no output schema, the description supplies what the schema cannot: that a persistent Library artifact is produced, that it costs one generation, and that nothing leaves the system. The main remaining gap is what the saved output contains and how the four templates differ in depth.

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 each of the six parameters, including the template enum and the business_profile_id requirement, is already documented. The description's mode list mirrors the enum but adds no syntax, format, or conditional guidance beyond it, so the baseline 3 applies.

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?

"Reviews ideas through expert perspectives, debate, market research or a concise core answer" gives a specific verb (reviews/stress-tests) and resource (an idea), and its four modes map cleanly onto the template enum. It is distinguishable from the write_* siblings, though it never explicitly says how it differs from planning tools like plan_priorities_and_data.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for critiquing a proposed idea rather than drafting copy. There is no explicit when-to-use, when-not-to-use, or statement of which sibling to pick for adjacent jobs like improving existing copy or designing an offer.

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