Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

현금영수증 매출 합계 조회

hometax__cash_receipt__sales__search_summary
Read-only

REQUIRES prior hometax__session__login call with same account_link_id. Search cash receipt sales annual summary. Use cmtt_yr for the target year. Optionally specify qrt (quarter 1-4) for quarterly breakdown. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 1소진

Input Schema

NameRequiredDescriptionDefault
qrtNoQuarter 1-4. Optional — omit for full-year summary.
cmtt_yrYesTarget year YYYY (e.g. '2025'). Required.
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/destructiveHint annotations, the description discloses the auth requirement (prior session login), a per-call token cost ('호출마다 토큰 1소진'), and full idempotency-key lifecycle semantics. That is meaningful context the annotations do not capture; only return format/pagination is unaddressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite is appropriately front-loaded, but the multi-sentence idempotency block is verbose and partly duplicates the schema's 'see the tool description' pointer. The trailing Korean token note is useful but tacked on rather than integrated.

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 read-only summary query with no output schema, the description covers auth, parameters, idempotency, and cost—enough for correct invocation. It does not describe the shape of the summary returned, but with no output schema that is the only notable gap.

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 coverage is 100% so baseline is already met, but the description adds real meaning beyond the schema for request_idempotency_key—explaining when to generate, reuse, and regenerate the key. Remaining params (cmtt_yr, qrt) are essentially restatements of the schema.

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?

States a specific verb and resource: 'Search cash receipt sales annual summary', with the quarterly vs annual distinction made explicit via qrt. It implicitly separates from the sibling hometax__cash_receipt__sales__search_history through the 'summary' framing, but does not name that sibling directly.

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?

Provides a hard prerequisite ('REQUIRES prior hometax__session__login with same account_link_id') and explains the optional quarterly breakdown, which gives usable invocation context. However, it never states when to prefer this summary over the sales/search_history sibling, so alternative selection is left to inference.

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

All XBOSS toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources