Skip to main content
Glama
Sign In
Mercari MCP Server

Mercari MCP Server

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get_purchases

Retrieve your purchase history on Mercari. Get details of past purchases with optional limit on number of records.

Instructions

View purchase history for the authenticated user

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax purchases to return (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must fully convey behavior. It only states 'View' (implies read-only) but lacks details on authorization beyond 'authenticated user', pagination, rate limits, or what data is returned (e.g., refunded purchases).

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?

The description is a single concise sentence that directly states the tool's purpose without extraneous words, earning high marks for efficiency.

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?

Given a simple tool with one optional parameter, the description is minimally adequate. However, it omits potential details like sorting, pagination mechanics, or return value structure, which would improve completeness.

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% with a single parameter 'limit' described as 'Max purchases to return (default 20)'. The description adds no additional meaning, meeting the baseline for full schema coverage.

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?

The description uses a specific verb (View) and resource (purchase history) and clearly distinguishes from sibling tools like get_sales (seller view), establishing it's for the buyer's perspective.

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?

The description implies usage for viewing own purchase history but does not explicitly state when to use this versus alternatives like get_sales or search tools. No guidance on prerequisites or context.

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