Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_get_payee_location

Read-only

Retrieve a single YNAB payee location by its ID, optionally within a specified plan or the configured default plan, to inspect where a payee is located.

Instructions

Get one payee location.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "payee_location_id": "<payee_location_id>"
    },
    "name": "ynab_get_payee_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
payee_location_idYesPayee location id from ynab_list_payee_locations.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds nothing: no note on requiring a valid plan, on error behavior when the id is unknown, or on freshness of the data, so it earns little credit above the annotations.

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?

It is a single short sentence with no wasted wording, and the key verb-resource pair is front-loaded. It is concise to the point of being under-specified rather than bloated.

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 annotations cover safety. Still, for a lookup tool in a large sibling set, the description gives no discriminator between fetching a payee location and fetching a payee or listing locations, leaving a genuine completeness gap.

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% and both parameters are documented, including the default-plan behavior for plan_id and the source of payee_location_id. The description contributes nothing beyond the schema, so the baseline of 3 applies.

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

Purpose3/5

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

The description states a specific verb and resource ('Get one payee location'), but it is essentially a restatement of the tool name with no additional distinguishing detail. It does not explain how a payee location differs from a payee, leaving the agent to infer that from sibling names alone.

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?

There is no when-to-use guidance, no mention of alternatives such as ynab_list_payee_locations or ynab_get_payee, and no note about prerequisites. The only routing help comes from the schema's parameter description referencing ynab_list_payee_locations as the id source, not from the description itself.

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