Skip to main content
Glama

spy_action

Direct a spy to travel to a city or launch a mission like counterspying, stealing tech boosts, or sabotaging production. Travel must be done first, then end the turn to activate missions.

Instructions

Send a spy to a city or launch a spy mission.

Args:
    unit_id: The spy's composite ID (from get_spies output)
    action: 'travel' to move spy to a city, or a mission type to launch a mission.
        Mission types: COUNTERSPY, GAIN_SOURCES, SIPHON_FUNDS, STEAL_TECH_BOOST,
        SABOTAGE_PRODUCTION, GREAT_WORK_HEIST, RECRUIT_PARTISANS,
        NEUTRALIZE_GOVERNOR, FABRICATE_SCANDAL
    target_x: X coordinate of the target city tile
    target_y: Y coordinate of the target city tile

Travel notes:
    - Valid targets: your own cities and city-states only.
    - Allied civ cities are NOT valid travel targets.
    - Travel is queued end-of-turn; spy position updates after turn ends.

Mission notes:
    - Spy must be physically IN the target city to launch any offensive mission.
    - Use 'travel' first, then end the turn, then launch the mission.
    - COUNTERSPY defends your own city (spy must be in your city).
    - get_spies shows which ops are available at the spy's current location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
unit_idYes
target_xYes
target_yYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full behavioral disclosure. It explains that travel is queued end-of-turn, spy position updates after turn ends, and missions require the spy to be physically in the target city. It does not mention potential side effects like diplomatic repercussions or cooldowns, but covers the essential behavior well.

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 well-structured with sections (Args, Travel notes, Mission notes) and is front-loaded with the main action. It is relatively concise given the complexity, but could be slightly tighter by removing redundant phrases like 'Valid targets: your own cities and city-states only' which is clear.

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?

Despite no annotations, the description is complete enough for an AI agent to use the tool correctly. It explains the workflow (travel then mission), valid targets, sequencing, and references get_spies for available ops. The presence of an output schema supplants the need to describe return values.

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

Parameters5/5

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

The input schema has no property descriptions (0% coverage), but the description fully explains each parameter: unit_id is the spy's composite ID from get_spies, action includes 'travel' and enumerated mission types, target_x and target_y are coordinates. This adds significant meaning beyond the schema.

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 description clearly states the tool's purpose: 'Send a spy to a city or launch a spy mission.' It distinguishes between two actions (travel and mission) and provides specific mission types, making it distinct from sibling tools like unit_action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use each action: valid travel targets (own cities and city-states, not allied civ cities), the need to travel first before missions, and the sequencing ('Use 'travel' first, then end the turn, then launch the mission'). It also mentions checking get_spies for available ops.

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/wrislin1/civ6-mcp'

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