Skip to main content
Glama

광고비 한도 보기

marketing__budget_limit__get

이 조직이 정한 광고비 한도(하루 예산 상한과 입찰가 상한, 원 단위)를 읽습니다. 정한 적이 없으면 비어 있는 한도를 돌려주며, 비어 있는 칸은 무제한이 아니라 그 금액을 바꾸는 요청을 막습니다. 한도는 광고 금액을 바꾸는 요청을 막는 기준이고 실제 하루 지출 상한을 보장하지 않습니다. 엑스보스에 저장된 설정을 읽기만 합니다. 외부 기관이나 광고 계정을 부르지 않으며 로그인이나 연동이 필요 없습니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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": "marketing__budget_limit__get"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

The description carries substantial behavioral detail beyond the annotations: it discloses that each call consumes one token, creates an XBOSS work item and stores the result, so the call is 'not purely read-only' despite reading settings (which agrees with readOnlyHint=false). It also states that no external institution or ad account is contacted, that empty budget fields block changes rather than act as a cap, and that the limits do not guarantee real daily spend. The only blemish is a small internal gap between 'reads stored settings only' and the later 'not purely read-only' caveat, but the description reconciles those two statements itself.

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 purpose is front-loaded and the sentences are individually clean, but the passage is long and repetitive in places (the read-only point is made twice: 'reads only' and then 'not purely read-only'). The most decision-relevant disclosure — that the call consumes a token and creates a work item — sits near the end, after the idempotency-key discussion.

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 single-optional-parameter tool with no output schema and one annotation, this is close to complete: it explains the return semantics of an unset limit, the blocking consequences of empty fields, the cost per call, and the idempotency-key contract. Only the explicit relationship to the companion write tool is missing, and that omission is real.

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

Parameters5/5

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

The schema description for the single parameter is just a pointer ('how to use it is in the tool description'), so this description must supply the semantics. It does: create and store the key before the first request for logged-in calls, resend the same value together with the same arguments only to recover an unanswered request, use a new value for a new execution, omit the key for trial calls without an account, and do not confuse it with the institution's separate idempotency_key field. That is more meaning than the schema provides, and the right kind.

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 first sentence states a specific verb and resource: it reads the organization's ad budget ceiling (daily budget cap and bid cap, in KRW). That is unambiguous and concrete. It is held back from a 5 because it never names the sibling that writes the same setting (marketing__budget_limit__set), even though this tool is only meaningful alongside it.

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 guidance is implicit rather than stated. The description does explain the key reading convention — empty fields mean 'requests that change this amount are blocked', not 'unlimited' — which is a real comprehension aid. But it never says when to call this tool rather than another, and does not clarify the read/write relationship with the sibling setter.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources