Skip to main content
Glama

내 미확정 접수 상태 조회

handam_public_get_request_status
Read-onlyIdempotent

접수자 본인(profileId + ownerCapability 보유자)이 접수한 주문 1건의 현재 상태를 조회합니다. 다른 사람의 주문이나 연락처·주소는 반환하지 않습니다. profileId만으로는 조회할 수 없습니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "orderId": "<orderId>",
      "profileId": "<profileId>",
      "ownerCapability": "<ownerCapability>"
    },
    "name": "handam_public_get_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYes
profileIdYes첫 접수 응답의 profile.profileId (조회 키일 뿐 권한이 아님)
ownerCapabilityYes첫 접수 응답에 한 번만 제공된 소유자 확인값. 클라이언트가 안전하게 보관해야 하며 다른 사용자와 공유하면 안 됩니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description goes beyond them by disclosing data minimization (no other users' orders, no contact or address data returned) and the composite authorization requirement, which are real behavioral facts not present in the annotations.

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?

Three short sentences, each carrying distinct information: what is read, what is not returned, and what is required to call it. No repetition of the title or annotations, and the scope statement is front-loaded.

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-record read with no output schema, the definition covers identity, authorization, and data exclusion adequately. It stops short of describing the returned status representation or what happens when ownerCapability is invalid or expired, which an agent would otherwise have to discover by calling.

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 67%, with profileId and ownerCapability already well documented in the schema; only orderId is bare. The description compensates by explaining that the two credentials together form the authorization key and that profileId alone is not sufficient, which is semantic meaning beyond the field-level docs.

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?

A specific verb (조회) plus a specific resource (a single order's current status) and an explicit scope restriction to the submitter's own request. The word '주문 1건' distinguishes it from the history-listing siblings, but no sibling is named explicitly, so differentiation is implied rather than stated.

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?

The description states a hard precondition — the caller must hold both profileId and ownerCapability, and profileId alone is insufficient — which guides correct invocation. It never says when to prefer this over handam_public_list_my_history or handam_public_apply_history, 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources