Skip to main content
Glama

findingsteel-steel-sections

List material densities

weight_materials
Read-onlyIdempotent

列出内置材质密度表(Q235/Q355、304、316、铝、铜)与默认值。List supported material densities.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
defaultYes
materialsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "default": {
      +      "type": "string"
      +    },
      +    "materials": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "density": {
      +            "type": "number"
      +          },
      +          "key": {
      +            "type": "string"
      +          },
      +          "nameEn": {
      +            "type": "string"
      +          },
      +          "nameZh": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "key",
      +          "nameZh",
      +          "nameEn",
      +          "density"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "materials",
      +    "default"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely new context: this is a closed, built-in set of materials with defined defaults, telling the agent no external data source is consulted.

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?

Very short and front-loaded, with the material list up front. The Chinese and English sentences are near-duplicates, a minor redundancy that costs a little efficiency but keeps the definition compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter enumeration tool, the description is complete: it names the domain, the covered materials, and the existence of defaults. An output schema exists, so return-value structure need not be explained.

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 tool takes zero parameters, which is the baseline 4 case. The description correctly signals a no-argument call by describing the result set rather than any input.

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?

States a specific verb+resource (list built-in material density table) and enumerates the actual materials covered (Q235/Q355, 304, 316, aluminum, copper) plus the presence of defaults. An agent can immediately tell this apart from the sibling weight_calculate, which computes rather than lists.

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 only implied: it is a reference lookup whose natural role is to supply density values before calling weight_calculate. There is no explicit when-to-use, when-not-to-use, or naming of an alternative (e.g., custom materials). Adequate but with a clear gap.

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.