ynab-mcpb

Overview Schema Source Related Servers Discussions Admin

ynab_diagnostic_info

Read-onlyIdempotent

Retrieve health, cache, security, and memory diagnostics to troubleshoot the YNAB MCP server and monitor its performance.

Instructions

Get comprehensive diagnostic information about the MCP server (health, cache, delta, security).

Args:

include_memory (boolean, optional): Include memory usage. Default: true.
include_environment (boolean, optional): Include env info. Default: true.
include_server (boolean, optional): Include server info. Default: true.
include_security (boolean, optional): Include security stats. Default: true.
include_cache (boolean, optional): Include cache metrics. Default: true.
include_delta (boolean, optional): Include delta cache info. Default: true.
response_format (string, optional): "json" or "markdown" (default: "markdown").

Returns: diagnostics object with requested sections.

Input Schema

Name	Required	Default
`include_cache`	No
`include_delta`	No
`include_memory`	No
`include_server`	No
`response_format`	No	markdown
`include_security`	No
`include_environment`	No

Output Schema

Name	Required	Description	Default
`cache`	No
`delta`	No
`memory`	No
`server`	No
`timestamp`	Yes
`environment`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.29.1Oct 26, 2026
- removedOutput schema / properties / cache / properties / lastCleanup / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / cache / properties / lastCleanup / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / environment / properties / token_preview / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / environment / properties / token_preview / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Addedv0.26.9May 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description doesn't need to restate it. The description adds useful defaults (all sections on by default, markdown output by default) but says nothing about output volume or whether diagnostics include sensitive values when include_environment/include_security are enabled.

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?

Purpose is front-loaded in a single clear sentence, followed by a compact Args block. The parameter list largely duplicates schema information but is the only prose source for it, so it earns most of its space; the trailing 'Returns' line is slightly wasted given an output schema exists.

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?

With an output schema present, return values need not be detailed, and the description covers every parameter plus defaults, which is the main completeness burden for a 7-param, 0%-coverage schema. What remains unstated is the practical context — when an agent should run this and any caution about environment/security data exposure.

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?

Schema description coverage is 0% — the JSON schema carries only types, defaults and one enum — so the description does the heavy lifting, naming all seven parameters and explaining what each include_* flag adds. It also restates the response_format enum values. Only minor gap: it doesn't clarify whether the include flags interact (e.g. whether security stats require server info).

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?

States a specific verb ('Get') and resource ('comprehensive diagnostic information about the MCP server') and enumerates the content domains (health, cache, delta, security). This is unmistakably distinct from every sibling, all of which operate on YNAB budget data rather than server internals.

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 only implied by the word 'diagnostic' — an agent can infer this is for health/troubleshooting checks, but the description never says when to reach for it or when a sibling (e.g. ynab_clear_cache) would be the better choice. No exclusions or prerequisites are stated.

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

Deploy Server