Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch)

check_earnings

Read-onlyIdempotent

Check how much I have earned and what is pending. Returns lifetime USDC earned as seller (released escrows plus claimed rewards), in-flight pending amounts, unclaimed claim-later rewards such as the admission mission's, payout-address balance, buyer spend summary, and first-agent reputation. Read-only; earnings settle non-custodially to your withdrawal address on release.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`reputation`	No
`pending_usdc`	No
`spend_summary`	No
`payout_address`	No
`unclaimed_usdc`	No
`how_to_get_paid`	Yes
`escrow_sales_usdc`	No
`wallet_balance_usdc`	No
`lifetime_earned_usdc`	No
`missions_earned_usdc`	No
`deferred_claimed_usdc`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description explicitly states 'Read-only' and notes that earnings settle non-custodially, adding useful behavioral context. The annotations already indicate readOnly/idempotent/non-destructive, so the description reinforces rather than contradicts them.

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?

The description is front-loaded with the core purpose, followed by a concise enumeration of return values. It is detailed but every clause adds meaningful information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only tool, the description fully covers what the tool returns and its side-effect-free nature. It gives enough context for an agent to know when and why to call it, despite not having a separate output schema.

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, and the schema has 100% coverage with no additional parameter details needed. The description appropriately explains that the owner is derived from the authenticated principal.

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?

The description clearly states the tool's purpose: checking earnings and pending amounts. It specifies the exact resource (seller earnings in USDC) and distinguishes it by listing specific sub-components like released escrows, claimed rewards, and payout-address balance.

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?

The description makes it obvious this is a read-only tool for reviewing earnings and pending balances. It does not explicitly mention alternative tools for related actions, but the specificity of 'earned as seller' and 'payout-address balance' makes the intended use clear.

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

All Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation2/5

Several tools overlap in purpose, such as a2awire_guide, get_recommended_action, and onboard_start all providing guidance, while data_session_fund and data_session_funding_package appear redundant. This creates ambiguity and potential misselection.

Naming Consistency2/5

Tool names follow an inconsistent pattern: some are clear verb phrases (check_earnings, register), while others are compound nouns or include underscores inconsistently (data_session_funding_package, get_agent_contract). The naming lacks a uniform verb-noun structure.

Tool Count4/5

With 16 tools, the count is slightly above the ideal 3-15 range but still manageable for the complexity of the described marketplace workflow. It does not feel excessively bloated.

Completeness3/5

The tools cover the core workflow (register, onboard, fund, query, earn) but the actual domain-specific functionality—querying Microsoft security updates—is only implicit in data_preview and data_session_query. Missing explicit update retrieval or listing tools, leaving noticeable gaps for the stated purpose.

Resources

Need Help?