Skip to main content
Glama

식약처 행정처분 이력 조회

lookup_mfds_disposition
Read-only

식품제조가공업(15124560)·식품판매업(15124559) 행정처분결과를 조회합니다. 승인 전파 전·오프라인이면 내장 대표 적발 패턴으로 안내하며, 업소명·대표자·연락처·주소·인허가번호는 반환하지 않습니다.

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

Input Schema

NameRequiredDescriptionDefault
rowsNo
limitNo
keywordNo위반법령·위반내용 키워드(예: '표시', '자가품질검사')
industryNoall
license_noNo인허가번호로 조회할 때(응답·저장에는 남기지 않음)
confirmed_onNo처분확정일 YYYYMMDD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover read-only / non-destructive / open-world, so the description earns credit for adding two things annotations cannot express: a data-quality caveat (before approval propagation it falls back to built-in representative violation patterns rather than live records) and a privacy contract (business name, representative, contact, address, and license number are never returned). It does not clarify how paging behaves or how the fallback results are marked in the payload.

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 tight sentences with no filler: the resource and scope come first, then the fallback caveat, then the excluded fields. Dense but front-loaded and easy to scan; it could be slightly clearer about which industry code maps to which enum value.

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 read-only lookup with six optional parameters and no output schema, the description covers purpose, scope limits, a fallback behavior, and a privacy guarantee — the pieces an agent most needs to decide whether to call it. The remaining gap is parameter-level guidance, especially the rows/limit distinction, which an agent cannot infer from the schema alone.

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

Parameters2/5

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

With only 50% schema description coverage, the description carries real burden but says nothing about parameters. Two similarly named pagination controls (rows max 100, limit max 20) are left unexplained, as are industry and confirmed_on semantics. The only adjacent content is the note that license_no is not returned, which is a privacy statement rather than query guidance.

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?

States a specific verb+resource: retrieving administrative disposition results (행정처분결과 조회) for two named food-business categories with their numeric industry codes. An agent can tell this is about enforcement/disposition history rather than labeling, recall, or import requirements. It stops short of naming which sibling to use instead when the question is about recalls (lookup_recall) or legal basis (get_legal_basis).

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 is only implied by the resource description — call it when you need disposition history for a food manufacturer or seller. There is no explicit when-not guidance, no statement of prerequisites (e.g. that a license number or confirmed date is optional), and no routing to alternatives such as lookup_recall or get_legal_basis.

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.