Skip to main content
Glama

Get batch prompt

mynahcast_get_batch_prompt
Read-onlyIdempotent

Ready-made weekly instruction to paste into your own agent. Returns text for a weekly cron (claude -p or codex exec). Nothing runs AI on our side.

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": {
      "brandId": "<brandId>"
    },
    "name": "mynahcast_get_batch_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdYes

Output Schema

NameRequiredDescriptionDefault
promptYes
brandIdYes
dailyCapYes
approvalModeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so safety is covered. The description adds genuinely new behavior context beyond that: it clarifies the tool returns text only and that no AI processing happens server-side, which rules out async generation or billing side effects.

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 payload ('Ready-made weekly instruction'), then the delivery mechanism, then the no-server-side-AI caveat. No filler; the only minor roughness is the slightly clipped phrasing of the first sentence.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What remains missing is any description of brandId semantics and any hint about what the returned prompt text contains or what inputs it expects, which matters for a tool whose entire output is opaque text.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — the single brandId carries only type/format/pattern, with no textual explanation. The description says nothing about what brandId identifies or how to obtain it (e.g., from list_brands), so the caller gets no help beyond guessing from the parameter name.

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 uses a specific verb+resource: it returns a ready-made weekly instruction text intended to be pasted into the caller's own agent/cron. That is concrete enough to separate it from the other getters, though it never names a sibling or explicitly contrasts itself with them.

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 implied rather than stated: 'paste into your own agent' and 'for a weekly cron' tell the agent the context in which this fits, but there is no explicit when-not guidance and no named alternative for cases where the agent wants the actual schedule or analytics instead.

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