Skip to main content
Glama

Get publishing state

mynahcast_get_autopilot
Read-onlyIdempotent

Whether publishing is stopped for a brand (stop_all), plus approval mode, daily cap and queued posts. Read-only. stopped=true means stop_all is on and nothing publishes until resume_all.

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

Input Schema

NameRequiredDescriptionDefault
brandIdYes

Output Schema

NameRequiredDescriptionDefault
queuedYes
brandIdYes
stoppedYes
dailyCapYes
stoppedAtYes
approvalModeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bare safety claim is redundant. The description earns credit for the semantic disclosure that stopped=true means stop_all is engaged and nothing publishes until resume_all — genuinely useful state-machine context not present in the annotations.

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 tight sentences, payload summary front-loaded, then the read-only and stopped-state semantics. Nothing redundant; every clause adds information.

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?

With an output schema present, the return shape need not be explained, and the description covers the key state semantics. What remains missing is how to source brandId and when this tool should be chosen over adjacent reads, which matters for a single-required-param lookup.

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% and the single required brandId parameter is documented only as a UUID pattern. The description says nothing more than 'for a brand' — no indication of where to obtain the ID or that list_brands supplies it, so it fails to compensate 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?

States a specific resource — a brand's publishing state — and enumerates the payload: stop_all flag, approval mode, daily cap, queued posts. An agent can tell this apart from account, analytics, or post fetches. It stops short of naming any adjacent alternative (e.g. the approval calendar) so it is not a full 5.

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: you call it to learn whether publishing is currently blocked and what the caps look like. There is no explicit when-to-use/when-not, no mention of pairing with resume_all as a follow-up action, and no guidance on where to get a brandId.

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