Skip to main content
Glama
shinichinomura

pesticide-mcp

by shinichinomura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PESTICIDE_DB_PATHNoDuckDB file path./data/pesticides.duckdb
PESTICIDE_SOURCE_DIRNoFAMIC ZIP/CSV save destination./data/raw

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
dataset_statusB

データセットの取り込み状態（件数・出典・取り込み日時）を返す。

search_pesticidesC

農薬名・登録番号・有効成分・農薬の種類から農薬基本情報を検索する。

結果は登録情報の検索結果であり、使用可否の判定ではない。

get_pesticide_by_register_noA

登録番号から農薬基本情報と適用情報の要約を取得する。

登録番号は ``12345`` と ``0012345`` の両方を受け付ける。
適用明細は含めず総件数と作物・病害虫の例のみを返す。
明細は ``get_applications`` に登録番号を渡して取得する。
get_applicationsC

作物名・病害虫雑草名・農薬名・登録番号などで適用情報を検索する。

各結果は使用時期・使用方法・使用回数などの根拠フィールドを含む。 使用可否の判定ではない。

check_registered_useA

指定条件に該当する登録行の候補を返す（使用可否の判定ではない）。

返す各候補には match_confidence と matched_fields が付く。
``allowed`` のような可否を断定するフィールドは決して返さない。
実使用前に必ず製品ラベルと最新の農薬登録情報を確認すること。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: checking registered use candidates, dataset status, application search, pesticide details by registration number, and general pesticide search. No overlap in functionality.

Naming Consistency5/5

All tools use consistent snake_case with a verb_noun pattern (e.g., check_registered_use, get_applications, search_pesticides). No mixed conventions or unclear abbreviations.

Tool Count5/5

Five tools is appropriate for a pesticide information server, covering essential query operations without being too few or excessive.

Completeness5/5

The tool set provides comprehensive coverage for searching and retrieving pesticide information, including status, registration details, applications, and usage candidates. References between tools (e.g., get_pesticide_by_register_no suggesting get_applications) show good integration.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources