Skip to main content
Glama

list_powders

List propellants in the served database (optionally filtered by manufacturer substring), with the GRT attributes the solver uses (Ba, Qex). Identity + published dimensional metadata only — NOT load data (rights-class discipline): no charge/velocity/pressure values are served by this tool.

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

Input Schema

NameRequiredDescriptionDefault
manufacturerNoOptional manufacturer substring filter (e.g. 'Hodgdon')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 (served database), the exact attribute classes returned, and a deliberate omission policy (no charge/velocity/pressure) framed as a rights constraint. It does not cover pagination or result-size behavior, which is the remaining gap.

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 scope, filter, returned attributes, and exclusions are packed into two tight sentences with the main purpose front-loaded. Some phrasing ("rights-class discipline") is internal jargon that costs a little clarity, but nothing is padded.

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?

There is no output schema, so the description must convey return content, and it does: identity, published dimensional metadata, and the Ba/Qex solver attributes. For a one-parameter read tool this is nearly sufficient, with only pagination/ordering 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?

Schema coverage is 100% and the single manufacturer parameter is already documented as a substring filter with an example in the schema. The description restates the same substring semantics without adding format, matching, or case-sensitivity details beyond it, so the 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 opens with a specific verb and resource ("List propellants in the served database") and enumerates the returned attribute set (Ba, Qex plus identity and dimensional metadata). It clearly separates itself from load-data siblings by stating no charge/velocity/pressure values are served. It stops short of naming which sibling to use for those values.

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 rather than stated: an agent learns this is the propellant-identity lookup and that it will not yield load data, and the optional manufacturer filter is noted. There is no explicit when-to-use versus a named alternative (e.g. generate_load_ladder or solve_internal_ballistics) for the excluded data.

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