Skip to main content
Glama

AICraft Injection Process

first_shot

Recommend a first-shot process. Costs 1 call. Required: polymer.polymer_abbreviation, mold.product_ave_thickness, machine.injector.injector_screw_diameter_mm.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does contribute the cost signal ('Costs 1 call') plus the required input set. Beyond that it says nothing about what the recommendation is based on, whether it is deterministic, or what happens when inputs are missing, which leaves meaningful behavioral gaps for an unannotated tool.

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?

Three short sentences with no filler: the action first, the cost second, the prerequisites third. Every sentence contributes information an agent needs, and the front-loading is correct.

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?

For a tool with no annotations and no output schema, the description covers the action, cost, and required inputs adequately enough to attempt a call. It stops short of describing the returned recommendation or how to interpret it, which is the main remaining gap given nothing else documents the response.

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?

The input schema declares no properties at all, so the description is the only source of parameter information, and it names three specific required field paths spanning polymer, mold, and machine objects. That is real added meaning over an empty schema, though it does not explain the expected units or value formats for those fields.

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 verb and resource: 'Recommend a first-shot process,' which tells an agent this produces initial process settings rather than a validation or optimization result. It does not distinguish itself from the siblings 'optimize' or 'schema,' but the core action is unambiguous.

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?

The phrase 'Required: polymer.polymer_abbreviation, mold.product_ave_thickness, machine.injector.injector_screw_diameter_mm' effectively states a precondition for calling the tool, and 'Costs 1 call' signals a budget constraint. However, there is no explicit statement of when to choose this over 'optimize,' or when the tool should not be used.

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.