Skip to main content
Glama
Sign In

materials

by com.spacemushroom
OverviewDiscussionsAdmin

Vehicles that use an engine

vehicles_for_engine
Read-onlyIdempotent

Which vehicles and stages use an engine, from stated relations, with the stage or role, the quote and the source: "where is the Merlin 1D used", "which vehicles fly the RL10". vehicle_known false means a source names a vehicle for this engine that is not a product here (only the name is kept). Accepts an id, title or alias (RL10, Merlin, BE-4).

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": {
      "engine": "<engine>"
    },
    "name": "vehicles_for_engine"
  }
}

Input Schema

NameRequiredDescriptionDefault
engineYesEngine product id, title or alias, for example spacex-merlin-1d or RL10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description's job is lighter. It adds genuine value by describing the return payload (stage or role, quote, source) and the edge case where vehicle_known=false means only a name was preserved because the vehicle is not a product in this dataset.

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?

The purpose is front-loaded and the example queries are packed efficiently into a colon-led list. The second sentence about vehicle_known is slightly dense and reads as a fragment, but no sentence is wasted.

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?

With no output schema and a single required parameter, the description carries the burden of describing results and does so at a high level, including the anomalous vehicle_known case. It stops short of showing the actual response shape, which would fully close the gap.

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?

Schema coverage is 100% and the single parameter is already documented with an id example. The description's note that an id, title or alias is accepted adds only the alias examples (RL10, Merlin, BE-4), which largely restate the schema, so baseline 3 applies.

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 direction of lookup: vehicles and stages that use a given engine, backed by stated relations. This makes the inverse relationship to the sibling engines_for_vehicle inferable without opening either schema, though that sibling is never named explicitly.

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?

Two concrete example queries ("where is the Merlin 1D used", "which vehicles fly the RL10") make the intended use case unambiguous. It does not state when *not* to use it or point at the reverse tool, so the guidance is clear but not exhaustive.

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