NanoParse

nanoparse_status

Check wallet balance, USDC balance, quota state, and whether the next /fetch call will succeed without payment. Use before spending — tells the agent exactly how much to fund.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`address`	No	The Ethereum wallet address to query (0x...).

Output Schema

TableJSON Schema

Name	Required	Description
`quota`	Yes
`funding_uri`	No
`usdc_balance`	Yes
`balance_error`	No
`balance_known`	No
`wallet_address`	Yes
`price_per_parse`	Yes
`usdc_balance_raw`	No	Balance in micro-USDC; null when the chain could not be read
`next_call_will_succeed`	No	null when the free tier is exhausted and the balance is unknown
`estimated_parses_remaining`	No	null when the balance is unknown — never 0, which would imply an empty wallet

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 4, 2026

addedOutput schema / description

Added value: +"Machine-readable status fields. This schema describes structuredContent — strict MCP clients validate structuredContent against it, so it must NOT require the result-envelope `content` array."

addedOutput schema / properties / balance_error

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / balance_known
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / content

Removed value: -{
-  "description": "Human-readable status report as text content",
-  "items": {
-    "properties": {
-      "text": {
-        "description": "Multi-line status report: wallet, USDC balance, price, estimated parses, free tier, funding URI",
-        "type": "string"
-      },
-      "type": {
-        "enum": [
-          "text"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "text"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / estimated_parses_remaining

Added value: +{
+  "description": "null when the balance is unknown — never 0, which would imply an empty wallet",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / funding_uri
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / next_call_will_succeed

Added value: +{
+  "description": "null when the free tier is exhausted and the balance is unknown",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / price_per_parse
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / quota
```
Added value: +{
+  "type": "object"
+}
```

removedOutput schema / properties / structuredContent

Removed value: -{
-  "description": "Machine-readable status fields",
-  "properties": {
-    "balance_error": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "estimated_parses_remaining": {
-      "type": "number"
-    },
-    "funding_uri": {
-      "type": "string"
-    },
-    "next_call_will_succeed": {
-      "type": "boolean"
-    },
-    "price_per_parse": {
-      "type": "string"
-    },
-    "quota": {
-      "type": "object"
-    },
-    "usdc_balance": {
-      "type": "string"
-    },
-    "usdc_balance_raw": {
-      "type": "string"
-    },
-    "wallet_address": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / usdc_balance
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / usdc_balance_raw

Added value: +{
+  "description": "Balance in micro-USDC; null when the chain could not be read",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / wallet_address
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "content"
-]New value: +[
+  "wallet_address",
+  "usdc_balance",
+  "price_per_parse",
+  "quota"
+]

First observedSep 1, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only inspection and discloses the useful behavioral fact that it predicts whether the next fetch succeeds without payment. It does not state permissions, rate limits, or whether the query is side-effect-free explicitly, leaving gaps for a zero-annotation 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 compact sentences, front-loaded with what is checked and followed by the usage rationale. No filler, every clause earns its place.

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?

An output schema exists, so return values need no explanation, and the description covers the four queried aspects plus the actionable outcome (how much to fund). The optional address parameter is left to the schema, a minor gap given 0 required params.

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 there is only one parameter, so the schema already documents the address fully. The description adds no meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 ('Check') and enumerates the exact resources returned: wallet balance, USDC balance, quota state, and payment-free fetch eligibility. This clearly distinguishes it from the sibling nanoparse_fetch, which spends, versus this which inspects.

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?

'Use before spending' gives a clear trigger condition, and the second clause frames it as the funding-decision step preceding /fetch. It does not explicitly name nanoparse_fetch as the alternative, but the pre-spend context makes the relationship unambiguous.

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

All NanoParse tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.