Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_get_api_status

Read-only

Check how many of the 200 hourly YNAB API requests have been used and inspect cache settings without making an API call.

Instructions

Show how many of the 200 hourly YNAB API requests have been used and cache settings. Makes no API call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context beyond that: this tool consumes none of the rate limit it reports, which is exactly the kind of behavioral detail an agent could not infer from 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?

Two short sentences, front-loaded with the primary value and the quota detail. The trailing 'and cache settings' is grammatically loose and slightly obscures whether cache settings are part of the same returned status, but there is no wasted wording.

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?

For a zero-parameter diagnostic tool with annotations and an output schema already describing the return payload, the description covers what is needed. The only minor gap is the vague 'cache settings' clause, which the description does not clarify.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey; the baseline for empty schemas applies. Nothing in the description misrepresents the (empty) input surface.

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?

The description states a specific verb ('Show') and a specific resource (hourly YNAB API request usage against the 200-request limit, plus cache settings), which is obviously distinct from the entity-fetching siblings. It stops short of an explicit contrast with those siblings, but the purpose is unambiguous.

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?

Usage is implied rather than stated: 'Makes no API call' signals the tool is safe to invoke without consuming the very quota it reports, which is a useful practical hint. However, it never says when to prefer calling this (e.g., before bulk operations) or that it is a diagnostic-only tool for this server alone.

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