Skip to main content
Glama

Get report

mynahcast_get_report
Read-onlyIdempotent

What went out (and what failed) in a date range, with links to the live posts. Range is by scheduled time; defaults to the last 7 days. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mynahcast_get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
brandIdNo

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
itemsYes
failedYes
upcomingYes
publishedYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the closing 'Read-only' is largely redundant. The genuinely additive behavior is the scheduled-time windowing and the 7-day default, plus the fact that failures are included — helpful, but thin for a reporting tool.

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 compact sentences, front-loaded with the outcome the caller gets, then the range semantics. No wasted wording.

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?

An output schema exists, so return values need not be described here, and the date parameters are covered. The unexplained brandId scope is the one notable omission for a three-parameter tool.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does explain the date bound semantics (keyed to scheduled time, default last 7 days). It adds nothing about brandId, which is the remaining 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 states a specific resource and scope: what was published and what failed within a date range, with links to live posts. That distinguishes it from list_posts or get_post by its success/failure reporting angle, though no sibling is named explicitly.

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?

It supplies useful operating context (defaults to the last 7 days, range keyed to scheduled time rather than publish time), which implies when to reach for it. It gives no explicit when-not guidance or pointer to an alternative such as get_analytics or get_post_timeline.

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