Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_get_airing_calendar

Read-onlyIdempotent

Retrieve all placement airings for a merchant between two dates across every product, ordered by start time and shown in each rule's time zone to answer what is on air.

Instructions

[Merchant] Every airing of the merchant's placements between from and to, across all products, ordered by start time and each in its rule's time zone. Answers "what is on air this week" in one call. The range may span at most 400 days.

Endpoint: GET /placements/calendar

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "payware_products_get_airing_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd of the range, after from, in the same forms
fromYesStart of the range: a date (YYYY-MM-DD, the start of that day in UTC) or an ISO-8601 instant with an offset, e.g. 2026-10-19T00:00:00+03:00
useSandboxNoUse the sandbox (the default) rather than production

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds real value on top: result ordering (by start time), per-item time zone handling, the 400-day cap, and the sandbox-vs-production default. It does not describe pagination or result volume for a potentially large calendar, which is the main remaining behavioral gap.

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?

Three sentences plus an endpoint line, with the scope and ordering front-loaded and zero filler. Every sentence carries a usable fact.

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?

For a read-only, 3-parameter range query with full schema coverage and rich annotations, the description is nearly sufficient: scope, ordering, time-zone semantics, span limit and environment default are all covered. It only leaves the result payload composition (which fields each airing carries) implicit, which matters somewhat given there is no output schema.

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 coverage is 100% and the schema already explains the from/to date forms, so the schema does the heavy lifting (baseline 3). The description contributes the cross-parameter 400-day span constraint, which is genuinely new meaning, but it says nothing further about useSandbox beyond what the schema states.

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 concrete verb+resource: every airing of the merchant's placements across all products, ordered by start time, each in its rule's time zone. That is specific enough to separate it from get_airing (single airing) and get_next_airings (upcoming), though it never names those siblings explicitly.

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

Usage Guidelines4/5

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

Gives a clear usage context — "Answers 'what is on air this week' in one call" — which signals this is the bulk-range tool rather than the single-item one. It adds the hard constraint (range at most 400 days) but names no explicit alternative or exclusion, so it stops short of a 5.

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