Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_logs_download_url

Read-onlyIdempotent

Generates a download URL for a gzipped JSON logs archive over a selected time range; a premium plan is required.

Instructions

[Merchant] Get download URL for logs archive. Premium plan required. Returns URL for downloading logs as gzipped JSON file.

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": "payware_logs_download_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd timestamp in ISO 8601 format (e.g., '2024-01-15T23:59:59Z'). Defaults to now.
fromNoStart timestamp in ISO 8601 format (e.g., '2024-01-15T00:00:00Z'). Defaults to 24 hours ago.
partnerIdNoPartner ID from payware dashboard. Uses PAYWARE_PARTNER_ID env var as default.partner_12345
privateKeyNoRSA private key for authentication. Uses environment-specific private key as default.
useSandboxNoRead the sandbox logs (default) or production's

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare this is a safe, idempotent read, so the description's job is to add context – and it does: a paid-plan gating requirement and the fact that the call yields a URL to a gzipped archive rather than inline log data. It stops short of saying whether the URL expires or how large the archive can be.

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 short sentences, front-loaded with the action, followed by the gating constraint and the return shape. No filler and nothing buried.

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 five optional parameters that all have defaults and no output schema, the description covers the essentials: what the call produces, the plan requirement, and the archive format. Minor gaps remain around URL lifetime and the sandbox default, but nothing critical for a correct invocation is absent.

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%, so the from/to window, sandbox flag, and credential parameters are already documented in structured form. The description adds nothing about the time-range semantics or the sandbox-vs-production default, so the baseline of 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?

The description names a specific verb and resource: get a download URL for the logs archive. It also states the payload format (gzipped JSON), which separates it from a log-querying sibling, though it never names payware_logs_query or payware_logs_status directly.

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 one real prerequisite, 'Premium plan required', which helps an agent decide whether the call can succeed. It gives no explicit when-to-use vs. when-to-use-another-tool guidance, so an agent must infer that this is the bulk-retrieval option rather than the query option.

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