Skip to main content
Glama

find_exobiology_targets

Identify organic-rich systems near a location or system, ranked by estimated exobiology turn-in credits, with body breakdowns and distance.

Instructions

Best exobiology targets near you: organic-rich systems with estimated turn-in.

Uses Spansh bodies search for organic-life bodies, ranks systems by estimated turn-in credits (body value x biology multiplier). Returns per-system body breakdown with distance and estimated value.

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": "find_exobiology_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
zNo
radius_lyNo
journal_dirNo
max_resultsNo
system_nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

B3.4/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 it does contribute real behaviour: the upstream data source (Spansh bodies search), the ranking formula (body value x biology multiplier), and the shape of results (per-system body breakdown with distance and estimated value). It omits operational traits an agent would want, such as whether a network call is required, latency/rate limits, or what happens when no organic bodies are found nearby.

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?

Three short sentences, front-loaded with the value proposition, then mechanics, then return shape. No filler, though the trailing return-format sentence partially duplicates the existing output schema.

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?

The presence of an output schema relieves the description of explaining return values, and the ranking logic is a useful addition. However, for a seven-parameter tool with zero schema documentation and no annotations, the total absence of parameter and prerequisite guidance leaves material gaps.

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% across seven parameters, yet the description only gestures at 'near you', which loosely implies the x/y/z coordinates and radius_ly. It never explains the coordinate frame, the default 50 ly radius, how system_name interacts with or overrides coordinates, what journal_dir supplies (presumably current location), or what max_results controls.

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 states a specific resource and outcome: organic-rich systems ranked by estimated exobiology turn-in credits, sourced from a Spansh bodies search. An agent can tell this is a discovery/ranking tool rather than a lookup. It does not explicitly contrast itself with the neighbouring get_exobiology_samples, so sibling differentiation is only implied.

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

Usage Guidelines3/5

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

Usage is implied by phrases like 'targets near you' and 'estimated turn-in', suggesting a planning/route-selection scenario, but there is no explicit when-to-use clause, no when-not-to-use, and no named alternative such as get_exobiology_samples or find_local_opportunities. The agent must infer the choice.

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