Skip to main content
Glama
datagokr-dev

datagokr

by datagokr-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fields

Read-only

Locate datasets containing every specified column. Filter by organization, data type, or count to get ranked metadata results.

Instructions

지정 컬럼을 모두 가진 데이터셋을 찾습니다. Find datasets matching ALL named columns. names 예시 / Example: ['위도', '경도']; n: 1~20; dtype: FILE/API/STD; org: 기관명. 반환은 search와 같은 메타데이터입니다. Returns ranked metadata as in search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
orgNo
dtypeNo
namesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.4
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With readOnlyHint=true, the safety profile is already declared, so the description only needs to add context. It contributes the n range (1~20), dtype values (FILE/API/STD), and that results are ranked metadata, but omits ranking basis, pagination, or matching/case behavior.

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?

Front-loads the core purpose, then parameter hints, then the return note. The bilingual duplication doubles length but each line carries unique, useful content rather than padding.

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?

An output schema exists, so return values need not be detailed, and the description still adds the 'ranked metadata as in search' note. Combined with readOnlyHint and full parameter hints, it is nearly sufficient despite the terse tool name.

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?

Schema coverage is 0%, so the description must compensate and largely does: it gives a names example (['위도','경도']), the n range (1~20), dtype enum values (FILE/API/STD), and explains org as an institution name. Only a precise meaning of dtype tokens is left implicit.

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 and resource: finding datasets that contain ALL named columns, which separates it from the generic 'search' sibling by its column-matching semantics. The reference to 'search' for return format also positions it relative to a sibling, though it does not fully spell out the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a column-based lookup but never states when to choose 'fields' over 'search' or the other retrieval siblings. No prerequisites, exclusions, or alternative-routing guidance are given.

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

Deploy Server

Other Tools