Skip to main content
Glama

mine

Mine resources from asteroids, ice fields, or gas clouds (Requires appropriate equipment: mining laser or loaded mining gun for ore, ice harvester for ice fields, gas harvester for gas clouds — keyed on the resource, not the POI type, so a gas cloud can hold ore a mining laser works. Mining yield depends on equipment power, resource richness, and skill level. get_poi and survey_system report supported_power, lock_minimum_stock and too_sparse per deposit, all computed for the hull you are flying: beam power above supported_power is capped rather than wasted, and a deposit below both a quarter of capacity and lock_minimum_stock cannot be worked at all (deposit_too_sparse). Mining power combines fitted lasers and loaded fitted mining guns, so unfit one or fit a finer one rather than adding another. Deep core POIs are exempt from that cutoff and always work down to zero. Which deposit a cycle hits is a random draw weighted by each deposit's richness and, as your mining skill grows, by its rarity. A fitted extraction filter (filter_* modules) removes its ore from that draw entirely, so every cycle targets one of the remaining deposits instead — that raises your yield of what you do want rather than wasting the cycle. If a filter rejects every deposit you could work at that POI, the cycle returns the filtered no-yield shape and mines nothing. Mining guns occupy utility slots. Each successful ore extraction consumes one charge from each loaded fitted mining gun. Empty mining guns contribute no power. Mining guns cannot harvest gas, ice, or radioactive ore. Compatible ammunition variants give identical mining performance. Combat ammunition effects do not apply. Use reload to refill magazines and get_ship to inspect ammunition.)

Input Schema

NameRequiredDescriptionDefault
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Despite the readOnlyHint=false annotation, the description exhaustively discloses mining mechanics: equipment requirements, yield calculation, deposit cutoff rules, filter effects, gun charge consumption, ammo behavior, and failure modes like deposit_too_sparse. It adds far more context than annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is front-loaded with purpose but then becomes a dense, unbroken paragraph of detailed mechanics. While informative, it is overly verbose and could be structured with bullet points for readability; some sentences (e.g., about combat ammunition) are tangential.

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

Completeness4/5

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

The description thoroughly covers mechanics, requirements, and edge cases, but with no output schema it does not describe the successful return value (e.g., what a mining cycle returns). It hints at failure shapes but leaves the normal output shape unspecified.

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?

The single parameter session_id is fully documented in the schema (100% coverage), so the description need not elaborate. It adds no extra meaning beyond the schema, which is acceptable given the high coverage.

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 begins with a specific verb and resource: 'Mine resources from asteroids, ice fields, or gas clouds.' It clearly distinguishes the action from informational siblings like get_poi and survey_system by contrasting what those tools report versus what this tool performs.

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?

It states equipment prerequisites and references related tools (reload, get_ship, get_poi, survey_system) for complementary tasks. However, it does not explicitly say when to choose mining over other actions or when not to use it, leaving some inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources