Skip to main content
Glama
Sign In
@localgov-jp/mcp-server

@localgov-jp/mcp-server

Official
by localgov-jp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_upcoming_sales

Retrieve auction properties with opening dates in the next N days (default 14, max 90). Sorted ascending for investment screening and calendar exports.

Instructions

近日開札予定の競売物件を一覧取得. List auctions whose opening_date falls within the next N days (default 14, max 90). Sorted ascending. Useful for investment screening / calendar exports.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50
days_aheadNoLookahead window in days, default 14

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses the time window (default 14, max 90), sorted ascending order, and forward-looking scope. It does not mention response format or pagination, but the core behavior is transparent enough for a read-only list 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 sentences, front-loaded with the verb 'List', includes essential details (time window, sorting, use cases). No filler or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must explain what the returned list contains. It only mentions sorting and time window, omitting response fields, pagination behavior, or any filtering side effects. This is inadequate for a tool with no structured output definition.

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 descriptions cover both parameters (limit, days_ahead) with defaults and constraints at 100% coverage. The description only repeats days_ahead defaults and max, adding no additional meaning beyond what the schema already provides.

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?

Description clearly states the tool lists auctions whose opening_date falls within the next N days, with a specific verb and resource. It distinguishes from sibling search_auctions by focusing on upcoming sales and mentions sorting and default/max values.

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?

Provides clear context for when to use the tool (investment screening, calendar exports) but does not explicitly exclude alternatives or name sibling tools. The use-case hints are sufficient for a basic list operation.

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