Skip to main content
Glama

spy_action

Move a spy unit to a target city or assign a spy mission such as counterspy, siphon funds, or steal tech boost. Coordinate with turn-based actions for effective espionage.

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
unit_idYes
actionYes
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?

Discloses important behavioral traits: travel is queued end-of-turn, spy position updates after turn, mission requires spy in target city. Does not mention potential failure or destruction, but given no annotations, description covers key behaviors adequately.

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?

Well-structured with clear sections (Args, Travel notes, Mission notes). Front-loaded summary, every sentence adds value, no redundancy. Appropriate length for the complexity.

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?

Given the complexity (multiple mission types, travel constraints, sequence), the description is complete. Covers input, behavior, valid targets, and references get_spies for available ops. Output schema exists, so return values are covered.

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?

With 0% schema coverage, description adds full meaning to all four parameters: unit_id (composite ID from get_spies), action (enum with travel and listed mission types), target_x/target_y (city tile coordinates). Provides actionable context beyond 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?

Description clearly states the tool sends a spy to a city or launches a spy mission, and lists specific mission types. It uses a specific verb+resource structure and distinguishes itself from sibling tools like unit_action or city_action.

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 clear when-to-use guidance: travel vs mission, valid travel targets (own cities/city-states, not allied civs), and sequencing (travel first, end turn, then mission). Lacks explicit comparison to sibling tools but is otherwise thorough.

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

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