Skip to main content
Glama
moma1992

Yaizu Smart City MCP Server

by moma1992
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_sample_endpoints

Retrieve example API endpoints for accessing Yaizu City's open data and smart city services, including facilities, disaster information, tourism, and municipal data.

Instructions

焼津市スマートシティAPIの主要なエンドポイント例を提供します。

Returns: str: エンドポイント例の一覧

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • mcp/server.py:597-646 (handler)
    The core handler function for the get_sample_endpoints MCP tool. Decorated with @mcp.tool() for automatic registration. Returns a static markdown string listing sample API endpoints categorized by topic (disaster, facilities, transport, etc.). No input parameters required.
    @mcp.tool()
async def get_sample_endpoints() -> str:
    """
    焼津市スマートシティAPIの主要なエンドポイント例を提供します。
    
    Returns:
        str: エンドポイント例の一覧
    """
    return """# 焼津市スマートシティAPI エンドポイント例

## 防災関連API
- `https://api.smartcity-yaizu.jp/v1/disaster/shelters` - 避難所情報
- `https://api.smartcity-yaizu.jp/v1/disaster/alerts` - 災害警報情報
- `https://api.smartcity-yaizu.jp/v1/disaster/hazardmap` - ハザードマップ情報

## 公共施設API
- `https://api.smartcity-yaizu.jp/v1/facilities/public` - 公共施設一覧
- `https://api.smartcity-yaizu.jp/v1/facilities/parks` - 公園情報
- `https://api.smartcity-yaizu.jp/v1/facilities/libraries` - 図書館情報

## 交通・インフラAPI
- `https://api.smartcity-yaizu.jp/v1/transport/buses` - バス路線情報
- `https://api.smartcity-yaizu.jp/v1/transport/parking` - 駐車場情報
- `https://api.smartcity-yaizu.jp/v1/infrastructure/roads` - 道路状況

## 観光・イベントAPI
- `https://api.smartcity-yaizu.jp/v1/tourism/spots` - 観光スポット
- `https://api.smartcity-yaizu.jp/v1/events/calendar` - イベントカレンダー
- `https://api.smartcity-yaizu.jp/v1/tourism/restaurants` - 飲食店情報

## 環境・センサーAPI
- `https://api.smartcity-yaizu.jp/v1/environment/weather` - 気象情報
- `https://api.smartcity-yaizu.jp/v1/environment/air-quality` - 大気質情報
- `https://api.smartcity-yaizu.jp/v1/sensors/water-level` - 水位センサー情報

## 使用方法
`execute_api_endpoint`ツールを使用してこれらのエンドポイントにアクセスできます。

例:
```
execute_api_endpoint(
    endpoint_url="https://api.smartcity-yaizu.jp/v1/disaster/shelters",
    method="GET",
    params='{"limit": 10}'
)
```

注: 実際のエンドポイントURLはAPIカタログで確認してください。
"""
  • mcp/server.py:597-597 (registration)
    The @mcp.tool() decorator on the get_sample_endpoints function registers it as an MCP tool.
    @mcp.tool()

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns 'a list of endpoint examples' as a string, which is minimal behavioral info. It doesn't describe whether this is a read-only operation, if it requires authentication, rate limits, or what the examples include (e.g., sample URLs, methods). For a tool with zero annotation coverage, this is insufficient.

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?

The description is appropriately sized and front-loaded: the first sentence states the purpose clearly, and the second specifies the return type. There's no wasted text, and it's structured efficiently. However, it could be slightly more concise by combining sentences, but it's already minimal.

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?

Given the tool has 0 parameters, 100% schema coverage, and an output schema exists (implied by 'Returns: str'), the description is somewhat complete but lacks depth. It states the purpose and return type, but for a tool with no annotations, it should ideally include more behavioral context (e.g., what the examples look like, if it's a static list). The output schema handles return values, so that's covered, but overall completeness is minimal.

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?

The tool has 0 parameters, and schema description coverage is 100% (though empty). The description doesn't need to add parameter semantics, so it meets the baseline. It correctly doesn't mention any parameters, which aligns with the schema. No extra value is added, but none is required for a parameterless tool.

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 clearly states the tool's purpose: 'provide examples of major endpoints for the Yaizu City Smart City API.' It specifies the verb ('provide') and resource ('endpoint examples'), though it doesn't explicitly differentiate from siblings like 'get_api_details' or 'list_saved_apis' which might also return endpoint information. The purpose is clear but lacks sibling 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 offers no guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'get_api_details' (which might provide detailed endpoint info) or 'execute_api_endpoint' (which might use endpoints), nor does it specify prerequisites or contexts for usage. There's no explicit or implied usage guidance beyond the basic purpose.

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/moma1992/smartcity-mcp'

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