Skip to main content
Glama
Sign In

Paylo

by com.usepaylo
OverviewDiscussionsAdmin

get_changelog

Read-onlyIdempotent

Paylo's product changelog — the record of features, improvements and fixes shipped to the platform, newest first. Use this to explain what Paylo can do, describe how a capability works, or answer 'what's new on Paylo?'. Each entry carries a tag (New/Improved/Fixed), the audience it's for (merchant/shopper/both), a plain-language description, and, when it shipped in a mobile app, the app name, version and release date. Filter by audience, status, a 'since' date, or free text.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries to return (default 200).
queryNoFree text over entry title and description, e.g. 'wishlist', 'POS', 'bookings'.
sinceNoISO date (YYYY-MM-DD); only entries shipped on or after it.
statusNoOnly this kind of change.
audienceNoKeep entries for sellers ('merchant') or buyers ('shopper'); either also includes shared ('both') entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real context beyond that: entries are ordered newest first and each carries a tag, an audience, a plain-language description, and optionally app name/version/release date — which is essential since there is no output schema.

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?

Front-loaded with the resource definition, then usage, then entry shape, then filters — a sensible order. Slightly verbose in the middle ('the record of features, improvements and fixes shipped to the platform' partially duplicates the later tag enumeration), but nothing is wasted enough to hurt.

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 no output schema, the description usefully enumerates the entry fields an agent will receive, and it covers all filters. It does not describe truncation behavior when the limit (default 200, max 500) is reached, which is the main remaining unknown for a list tool.

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 description coverage is 100%, so all five parameters are already documented with defaults, bounds, ISO format guidance and enum meanings. The closing sentence largely restates the schema's filters without adding syntax or interaction rules, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Paylo's product changelog') with concrete scope: newest-first record of features, improvements and fixes shipped to the platform. No sibling tool touches this resource, so the agent can distinguish it immediately from search_products or get_product.

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?

Names three concrete use cases ('explain what Paylo can do', 'describe how a capability works', 'answer what's new on Paylo'). It does not say when NOT to use it or which sibling to prefer for capability detail, so a small navigation gap remains.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Paylo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources