Skip to main content
Glama

주문 입력 스키마 조회

handam_public_get_order_schema
Read-onlyIdempotent

미확정 꽃 주문 초안의 입력 스키마, 상품 카탈로그 라벨, 제출 필수 항목, 전화번호 형식, 멱등(requestId) 규칙을 반환합니다. 고객 정보는 포함되지 않습니다.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral fact beyond that: no customer information is included in the response, which matters for privacy and for what the caller can rely on. It does not describe response shape or size, but the safety and content-scope gaps are largely closed.

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

Conciseness4/5

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

Two sentences, no filler, with the substantive return contents front-loaded and the privacy caveat placed last where it belongs. The first sentence is a dense comma-separated enumeration, which is efficient but slightly harder to scan than a short bulleted split would be.

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?

With no output schema, the description carries the burden of saying what comes back, and it does so by enumerating five distinct returned elements. Combined with the explicit note that customer data is excluded, an agent has enough to decide whether to call it. Missing only a pointer to the sibling that consumes this 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 input schema is an empty closed object, so there is nothing for the description to disambiguate. Baseline for a parameterless tool applies; no misleading parameter hints are present.

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 description names a specific verb and resource: it returns the input schema for an unconfirmed flower order draft, along with catalog labels, required submission fields, phone format, and requestId idempotency rules. An agent can tell this is a metadata/discovery read rather than the actual submission done by sibling handam_public_submit_flower_request. It never names that sibling explicitly, so differentiation is inferable 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?

There is no explicit when-to-use or when-not-to-use clause. Usage is only implied by the content list — an agent can infer this should be called before constructing a submission payload. No routing to alternatives such as submit_flower_request or preview_confirmation is given.

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