Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_payee_locations

Read-only

List GPS locations recorded for payees by the YNAB mobile app. Filter by payee and paginate results to review where transactions were made.

Instructions

List GPS locations recorded for payees by the YNAB mobile app.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return.
offsetNoRows to skip (use next_offset from a prior call).
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
payee_idNoOnly locations for this payee (from ynab_list_payees).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful provenance (locations come from the mobile app, implying coverage may be incomplete), but says nothing about pagination, empty results, or how limit/offset interact.

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?

A single front-loaded sentence with no filler or hedging. It is tight, though its brevity is part of the reason the usage and pagination guidance is missing.

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?

An output schema exists, so return values need not be explained, and all four parameters are documented in the schema. What is missing is list-tool context an agent needs: whether paging is expected and how to continue with next_offset, and how this differs from the single-location sibling.

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 limit, offset, plan_id and payee_id are already fully documented in the schema, including the cross-reference to ynab_list_plans and ynab_list_payees. The description adds no parameter meaning beyond that, which is the baseline case.

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?

A specific verb ("List") plus a precisely scoped resource ("GPS locations recorded for payees by the YNAB mobile app") tells an agent exactly what comes back. It stops short of distinguishing itself from the sibling ynab_get_payee_location, which retrieves one location, so the plural-vs-single split is left implicit.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites about needing a payee_id or default plan, and no pointer to the single-location sibling for the one-record case. Usage is only inferable from the tool name.

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