Skip to main content
Glama
Sign In

materials

by com.spacemushroom
OverviewDiscussionsAdmin

Engines used by a vehicle

engines_for_vehicle
Read-onlyIdempotent

Which engines a launcher, stage or spacecraft uses, from relations a source states (engine part of vehicle, vehicle carries engine). Each engine comes with its stage or role (role, note), the quote and source, its makers and suppliers, and the material ids in it, so you can go on to get_product for the engine or products_using_material for its alloys. engine_known false means a source names the engine for this vehicle but the engine is not a product here yet (only its name is kept). Accepts an id, title or alias (F9, SLS).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vehicle": "<vehicle>"
    },
    "name": "engines_for_vehicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
vehicleYesVehicle product id, title or alias, for example ula-vulcan-centaur or Falcon 9

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds the return shape (stage/role, note, quote, source, makers, suppliers, material ids) plus the engine_known=false edge case where only a name is retained. The only missing behavior is result ordering/pagination or empty-result handling.

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?

Purpose is front-loaded in the first clause, and each following sentence carries distinct payload: return contents, follow-on tools, and the engine_known=false edge case. Size is proportionate to the amount of information conveyed.

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?

A single-parameter read tool with no output schema is well served by a description that enumerates what comes back. Coverage is nearly complete; only empty-result and ordering behavior are unstated.

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

Parameters4/5

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

Schema coverage is 100% and already states 'Vehicle product id, title or alias', so the baseline is 3. The description adds concrete alias examples (F9, SLS) that supplement the schema's id/title examples, giving marginal extra meaning.

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 opens with a specific verb+resource: 'Which engines a launcher, stage or spacecraft uses', and adds provenance ('from relations a source states') plus the exact relation types. That is enough to tell it apart from the inverse sibling vehicles_for_engine without opening a schema.

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 gives clear usage context and forward paths ('so you can go on to get_product for the engine or products_using_material for its alloys'), which tells the agent what to do with the result. It stops short of an explicit when-not or naming vehicles_for_engine as the reverse lookup, so no exclusion guidance.

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

All materials toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources