Skip to main content
Glama

근거 조항 조회

get_legal_basis
Read-only

코퍼스에 수록된 법령 조항의 요지·시행일·원문 URL을 반환합니다.

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": {
      "law": "<law>"
    },
    "name": "get_legal_basis"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawYes
articleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description's real contribution is disclosing the return payload (gist, effective date, source URL), which matters because no output schema exists. It says nothing about failure behavior for an unknown law/article or about any rate or authentication constraints.

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?

It is a single front-loaded sentence with zero filler, and the return-content list is packed efficiently. Brevity here shades into under-specification rather than waste, but nothing in the text is extraneous.

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?

Because no output schema exists, the description's enumeration of returned fields is valuable and largely fills that gap. However, for a tool with two fully undocumented parameters and no guidance on how to choose between lookups, the definition is only partially complete.

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?

Both parameters ('law' and 'article') have 0% schema description coverage, so the description carries the full burden — yet it never names them. It gives no format for the law identifier, no example article value, and no hint that 'article' is optional while 'law' is required, so an agent must guess at the input shape.

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 combination in '법령 조항의 요지·시행일·원문 URL을 반환합니다' — it retrieves a statute article plus its gist, effective date, and source URL. That is far more concrete than the title alone. It does not, however, distinguish this retrieval from lookup-style siblings such as lookup_hs_requirements, leaving the agent to infer which lookup to pick.

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 phrase '코퍼스에 수록된' implicitly scopes the tool to laws present in the local corpus, which is a useful boundary hint. There is no explicit when-to-use, when-not-to-use, or fallback guidance, and nothing tells the agent what to do if the article is absent from the corpus.

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.