Skip to main content
Glama

Korea Court Auction (법원 경매 예상 낙찰가)

Send feedback

send_feedback

Send a short note (at most 1000 characters) about the service or one item to the operator. Use this when: the person reports a wrong value or a missing feature. 누구나 쓸 수 있습니다.

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": {
      "text": "<text>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
item_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent, closed-world). The description adds the delivery target (the operator) and the untranslated line "누구나 쓸 수 있습니다," which signals no special permission is needed. It says nothing about what happens after submission, whether a response comes back, or any rate limit.

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?

Three short sentences, front-loaded with the action and the limit before the usage condition. The Korean sentence is brief but breaks the otherwise single-language framing, which is a minor structural blemish rather than bloat.

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

Completeness3/5

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

For a two-parameter tool with no output schema, the essentials — what it does, when to use it, who receives it, length limit — are present. What is missing is the outcome/acknowledgment behavior and the precise role of item_id versus omitting it for service-level feedback.

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

Parameters3/5

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

Schema description coverage is 0%, so the description has to carry both parameters. It clarifies `text` as a short note about the service or one item and repeats the 1000-char ceiling, but `item_id` is never explicitly explained — its meaning is only inferable from "or one item." That is partial compensation for the coverage gap.

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?

Specific verb and resource: "Send a short note ... about the service or one item to the operator." It also scopes the two variants (service-level vs. item-level) that map to the optional item_id. It stops short of naming or contrasting any sibling tool, which is why it lands at 4 rather than 5.

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?

"Use this when: the person reports a wrong value or a missing feature" gives concrete triggering conditions tied to user-reported problems. There is no when-not guidance and no alternative tool is named for the cases this tool is not meant to cover.

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