Skip to main content
Glama

discover_tools

List all tools wired in this MCP build to identify available functions for land analysis, regulation verification, and permit search.

Instructions

List all currently wired tools in this MCP build.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'discover_tools' tool. It is an inline async arrow function that returns static text listing all available tools in the korean-land-mcp v2.0 build. No imported helper — the logic is entirely inline.
    server.tool(
      "discover_tools",
      "List all currently wired tools in this MCP build.",
      {},
      async () => ({
        content: [
          {
            type: "text" as const,
            text: [
              "korean-land-mcp v2.0 — V-World backed, mock fallback REMOVED",
              "",
              "Tools:",
              "- resolve_parcel(query): address|PNU → canonical parcel",
              "- get_zoning(query): 용도지역·지구·구역 + 토지거래허가구역",
              "- get_district_plan(query): 지구단위계획 + 개발행위허가제한",
              "- get_urban_facility(query): 도시계획시설 9개 카테고리",
              "- get_other_law_designations(query): 38개 개별법령 지정 (국계법 76조⑤ 우선위임 힌트 포함)",
              "- get_land_attributes(query): 지목 파싱 + 공시지가 + 건물 유무",
              "- analyze_parcel(query): 위 전체를 1회 호출로 체이닝",
              "",
              "Legal citations (법령·조례 원문) are intentionally out of scope — use korean-law MCP.",
            ].join("\n"),
          },
        ],
      })
  • The schema for 'discover_tools' is an empty object {} — no input parameters are accepted.
    {},
  • src/server.ts:93-118 (registration)
    Registration of the 'discover_tools' tool on the McpServer instance via server.tool().
    server.tool(
      "discover_tools",
      "List all currently wired tools in this MCP build.",
      {},
      async () => ({
        content: [
          {
            type: "text" as const,
            text: [
              "korean-land-mcp v2.0 — V-World backed, mock fallback REMOVED",
              "",
              "Tools:",
              "- resolve_parcel(query): address|PNU → canonical parcel",
              "- get_zoning(query): 용도지역·지구·구역 + 토지거래허가구역",
              "- get_district_plan(query): 지구단위계획 + 개발행위허가제한",
              "- get_urban_facility(query): 도시계획시설 9개 카테고리",
              "- get_other_law_designations(query): 38개 개별법령 지정 (국계법 76조⑤ 우선위임 힌트 포함)",
              "- get_land_attributes(query): 지목 파싱 + 공시지가 + 건물 유무",
              "- analyze_parcel(query): 위 전체를 1회 호출로 체이닝",
              "",
              "Legal citations (법령·조례 원문) are intentionally out of scope — use korean-law MCP.",
            ].join("\n"),
          },
        ],
      })
    );
Behavior4/5

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

With no annotations, the description carries full burden. It explicitly states 'list,' indicating a read-only operation, though it does not formally declare side-effect safety.

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

Conciseness5/5

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

Single sentence, 8 words, perfectly front-loaded. Every word is meaningful with no redundancy.

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?

Given the tool's simplicity (no parameters, no output schema, no annotations), the description is adequate. It could optionally mention return format but is complete enough for an agent.

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?

No parameters exist (0 parameters, 100% schema coverage). Baseline 4 applies; description adds no parameter info, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (list) and the resource (currently wired tools). It distinguishes itself from sibling tools which are specific domain tools.

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?

The description implies use when needing to discover available tools. No alternatives exist for this meta-function, so no exclusions needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/UrbanWatcherKr/korean-land-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server