Skip to main content
Glama

This Weekend (이번 주말)

제보 검토 결과

get_report_status
Read-onlyIdempotent

[이번 주말: 축제·공연·전시 찾기] 보낸 제보가 검토 중인지, 반영됐는지, 반려됐는지 알려 줍니다. 반려됐으면 운영자가 적은 사유도 함께 줍니다. 제보할 때 받은 reportId와 editKey가 있어야 합니다.

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": {
      "reportId": "<reportId>",
      "editKey": "<editKey>"
    },
    "name": "get_report_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
editKeyYes제보할 때 받은 editKey.
reportIdYes확인할 제보의 reportId.

Output Schema

NameRequiredDescriptionDefault
toolYes이 제보를 고칠 때 부르는 도구.
fieldsYes지금 저장된 제보 내용.
reasonYes반려 사유. 반려됐을 때만 있고 아니면 null입니다.
eventIdYes반영된 행사의 id. 승인됐을 때만 있고 아니면 null입니다.
messageYes
reportIdYes제보의 접수 번호. 고쳐서 다시 접수한 제보면 가장 최근 접수 번호입니다.
canReviseYestrue면 tool에 적힌 도구에 reportId와 editKey를 넣어 고칠 수 있습니다.
revisionOfYes반려된 제보를 고쳐 다시 접수했다면 반려된 이전 접수 번호입니다. 아니면 null입니다.
reviewStatusYespending은 검토 전, approved는 반영됨, rejected는 반영하지 않음입니다. already_listed면 null입니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds value by disclosing response content (status plus operator-written rejection reason) and the credential requirement. It stops short of saying what happens with an invalid or expired editKey, which matters for a key-gated lookup.

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 three substantive sentences are tight and front-loaded with the status meaning. The bracketed festival tag is off-topic padding that wastes the highest-attention position on information irrelevant to this tool.

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?

Although an output schema exists, the description usefully summarizes what comes back (status categories and the rejection reason), and it names the required credentials, which is enough for an agent to call it correctly. Only error behavior for a bad key is left unstated.

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 100%, so both parameters are already documented and the baseline is 3. The description only adds that the values come from the submission step, which mildly reinforces the schema text but supplies no new format or constraint detail.

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 core sentence states a specific verb and resource: it reports whether a submitted report is under review, approved (reflected), or rejected, and returns the operator's rejection reason. That distinguishes it from submit_event and report_event_change. The leading bracket tag '[이번 주말: 축제·공연·전시 찾기]' is unrelated to this tool and blurs the opening.

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?

It states a prerequisite ('제보할 때 받은 reportId와 editKey가 있어야 합니다') and implies the tool is used after submitting a report, which is genuine usage context. However, it never names an alternative or says when not to call it, so the agent must infer the position in the flow.

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