Skip to main content
Glama
nori1173-ops

SaaS_A MCP Server

by nori1173-ops

export_observation_data

Export observation data history as a CSV file saved to your local path, with a summary preview of rows, columns, and date range. Filter by tenant, group, device, and dates to get exactly the needed records.

Instructions

受信データ履歴を CSV でエクスポートします。

tenant_id は list_tenants で、group_cd は list_groups で、device_cd は list_devices で 取得してください。全件を対象にする場合は group_cd / device_cd に all を指定します。

必要な権限レベル: システム管理者(user_level=1)、テナント管理者(user_level=2)、 現場管理者(user_level=3)。権限が不足すると 403 になります。

CSV 本文はそのまま返しません(コンテキストを使い切るため)。 既定では行数・カラム名・先頭20行のプレビュー・データ期間の要約を返し、 CSV 本体は UTF-8 のファイルとして保存してその絶対パスを返します。 save_path を指定するとそのパス(絶対パスのみ・ディレクトリ可)へ、 未指定なら一時ディレクトリへ保存します。既存ファイルは上書きせず別名で保存します。 分析にはこのファイルを使ってください。

取得件数が API の上限を超えると 400 になります。その場合は期間を短くするか、 device_cd を all から個別の地点に絞って再実行してください。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoレスポンスの言語(ja / en)ja
end_dateYes終了日(YYYY-MM-DD)。未来日は API 側で現在時刻に丸められる
group_cdYes現場CD。全現場を対象にする場合は all
device_cdYes地点CD。全地点を対象にする場合は all
save_pathNoCSVの保存先の絶対パス(ファイル名またはディレクトリ)。相対パスはエラー。未指定なら一時ディレクトリに保存してパスを返す
tenant_idYesテナントID(UUID)。list_tenants で取得できる
start_dateYes開始日(YYYY-MM-DD)
output_typeYes表示項目形式(raw_data=生値、formatted_data=整形データ)
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Richly discloses behavior beyond annotations: the CSV body is intentionally not returned, a preview with row count/column names/first 20 rows is returned, the file is saved to a temp directory unless save_path is set, existing files are not overwritten, and insufficient permissions cause a 403. This gives the agent a clear mental model of side effects and failure modes.

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?

The description is front-loaded with the core purpose, then organized into lookup guidance, permissions, output behavior, and error handling. Every sentence carries actionable information; nothing is redundant or filler despite the length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with no output schema and minimal annotations, the description covers the essentials: what is returned, how files are saved, permission requirements, ID sourcing, and error recovery. An agent can invoke this tool and interpret its result correctly without external context.

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 100%, so the baseline is 3. The description adds value by telling the agent where to source group_cd and device_cd (list_groups/list_devices), which the schema does not, and by explaining save_path overwrite behavior. The 'all' special value and absolute-path rule are already in the schema, so the added value is meaningful but not extensive.

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 first sentence states a specific verb and resource: export received data history as CSV. It also clarifies the actual deliverable (a saved UTF-8 file and absolute path, not the CSV body), which immediately distinguishes it from the sibling list_* 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?

Provides strong usage context: tells the agent to obtain tenant_id/group_cd/device_cd from specific list_* tools, explains the 'all' option for full datasets, and gives recovery guidance when the API limit returns 400. It does not explicitly frame when not to use this tool, but no sibling is a true alternative for export, so this is a minor gap.

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

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/nori1173-ops/iot-saas-readonly-mcp'

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