Exports atlas data for a time window, bundling thinned GPS tracks, events, and geotagged photos for map apps and vlogs.
一站式打包某时间窗的 atlas 数据: {track(抽稀GPS), events(逗号分隔的模态 名可选过滤), photos(带坐标照片)}。地图类应用 (Life Atlas/vlog) 的数据源。
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | ||
| start | Yes | ||
| max_points | No | ||
| modalities | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
无 annotations，描述需承担全部行为披露义务。仅说明打包内容，未提权限要求、数据量上限行为、返回结构或是否只读等行为特征。
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
单句结构，先点明操作再以括号列出组成部分，信息密度高且无冗余。
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
虽有 output schema，返回内容无需描述，但参数语义覆盖 0%、无 annotations，加上 4 个参数的行为细节缺失，整体对正确调用而言仍不充分。
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
schema 描述覆盖率 0%，4 个参数 (start/end/max_points/modalities) 在 schema 中仅有无描述的字符串/整数字段。描述补充了 events 模态名可过滤及 track 抽稀，暗含 modalities 与 max_points 语义，但仍未说明 start/end 格式、max_points 含义与默认值等，补偿不足。
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
使用清晰具体的动词+资源，说明是打包某时间窗的 atlas 数据，并逐项列出所含内容 (track/events/photos)。未与其他兄弟工具 (如 lifedb_geo_track、lifedb_query_month) 做区分。
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
说明适用于地图类应用 (Life Atlas/vlog)，暗示使用场景，但未给出何时应选用此前工具而非 lifedb_geo_track 等替代项，也无排除条件。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.