Skip to main content
Glama

get_exobiology_samples

Retrieve exobiology sample status from local journals, including organic discoveries, FSS completion, and estimated turn-in credits using EDSM system values.

Instructions

Exobiology sample status: discovery, FSS progress, estimated turn-in credits.

Reads local journals for FSSAllBodiesFound / ScanOrganic / SAAScanComplete events. When FSS complete, uses EDSM estimated system value for turn-in credits. community_discovered=True means FSS complete OR EDSM has catalogued bodies (others discovered before you).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_exobiology_samples"
  }
}

Input Schema

NameRequiredDescriptionDefault
journal_dirNo
system_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the data source (local journals), the exact event types consumed (FSSAllBodiesFound / ScanOrganic / SAAScanComplete), and the external EDSM dependency for credit estimates. The only shortfall is that it does not state read-only behavior or latency/caching expectations explicitly, though 'Reads local journals' strongly implies a safe read.

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?

Front-loaded status line followed by mechanism, with no filler sentences. The final sentence defining community_discovered=True is dense but earns its place by decoding an output field the agent would otherwise misread.

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?

An output schema exists, so return values needn't be explained, and the behavioral mechanism is well covered. However, for a tool with zero annotation coverage and two entirely undocumented parameters, the description should say what the parameters do — that omission leaves a meaningful hole.

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

Parameters2/5

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

Schema description coverage is 0% and there are two parameters (journal_dir, system_name), yet the description never mentions either. It does not say whether system_name filters output or triggers an EDSM lookup, nor what the default journal_dir means — a real gap given the schema provides no titles beyond raw property names.

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 opens with a specific verb+resource: it reports exobiology sample status (discovery, FSS progress, estimated turn-in credits). That is clearly distinct from a targeting tool like find_exobiology_targets, though it never names a sibling to make the contrast explicit.

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?

There is no when-to-use or when-not-to-use guidance; the text explains mechanism rather than routing. An agent must infer that this is the status-reporting counterpart to find_exobiology_targets purely from the tool names.

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