Skip to main content
Glama

flyTo

Navigate to specific geographic coordinates with animated camera transitions in 3D globe visualization.

Instructions

飞行到指定经纬度位置(带动画过渡)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
longitudeYes经度(-180 ~ 180)
latitudeYes纬度(-90 ~ 90)
heightNo相机高度(米),默认 50000
headingNo航向角(度),0 为正北
pitchNo俯仰角(度),-90 为正下方
durationNo飞行动画时长(秒)

Implementation Reference

  • The actual implementation of the flyTo functionality that manipulates the Cesium viewer camera.
    export function flyTo(viewer: Cesium.Viewer, params: FlyToParams): Promise<void> {
      const {
        longitude,
        latitude,
        height = 50000,
        heading = 0,
        pitch = -45,
        roll = 0,
        duration = 2,
      } = params
    
      validateCoordinate(longitude, latitude, height)
    
      return new Promise((resolve) => {
        viewer.camera.flyTo({
          destination: Cesium.Cartesian3.fromDegrees(longitude, latitude, height),
          orientation: {
            heading: Cesium.Math.toRadians(heading),
            pitch: Cesium.Math.toRadians(pitch),
            roll: Cesium.Math.toRadians(roll),
          },
          duration,
          complete: resolve,
        })
      })
    }
  • The tool registration in the bridge class, which dispatches 'flyTo' actions.
    case 'flyTo':
      await this.flyTo(p as FlyToParams)
      return { success: true, message: 'Camera flew to target position' }
Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions animation ('带动画过渡') which is valuable behavioral context, but doesn't disclose other important traits: whether this is a read-only or mutating operation, what permissions might be needed, what happens if parameters are invalid, or what the visual outcome looks like. For a tool that presumably changes the camera view, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient Chinese sentence that states the core purpose with one additional behavioral detail (animation). Every word earns its place with zero waste.

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 6 parameters with full schema coverage and no output schema, the description provides the basic purpose and one behavioral trait (animation). However, for a view manipulation tool with no annotations, it should ideally mention more about the visual effect, error conditions, or relationship to other view tools to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 6 parameters thoroughly with ranges, defaults, and meanings. The description adds no parameter-specific information beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('飞行到' - fly to) and the target ('指定经纬度位置' - specified longitude/latitude position), with the additional detail of animated transition. It distinguishes from siblings like 'setView' or 'zoomToExtent' by specifying animation. However, it doesn't explicitly contrast with all possible alternatives.

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 provides no guidance on when to use this tool versus alternatives like 'setView' (which might set view without animation) or 'zoomToExtent' (which zooms to bounds). There's no mention of prerequisites, typical use cases, or when not to use it.

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/gaopengbin/cesium-mcp'

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