Skip to main content
Glama

Tile grid with joints

bpj_material_tile_joint_grid
Read-onlyIdempotent

Find complete tiles per axis and remaining edge space in a rectangular area with internal joints only.

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": {
      "fieldW": "<fieldW>",
      "fieldH": "<fieldH>",
      "tileW": "<tileW>",
      "tileH": "<tileH>",
      "joint": "<joint>"
    },
    "name": "bpj_material_tile_joint_grid"
  }
}

Input Schema

NameRequiredDescriptionDefault
jointYes
tileHYes
tileWYes
fieldHYes
fieldWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful constraint that only internal joints are considered, but it does not describe return values, edge-case behavior, or calculation assumptions.

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 definition is a single front-loaded sentence with no wasted wording. It is appropriately concise, though its terseness contributes to the missing parameter and output clarity.

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

Completeness2/5

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

For a calculation tool with no output schema and no parameter descriptions, the description is incomplete. It states what is computed in general terms but does not explain the result shape, units in practice, or how the five required inputs determine the tile counts and edge space.

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

Parameters2/5

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

With 5 parameters and 0% schema description coverage, the description should compensate, but it does not explain what fieldW, fieldH, tileW, tileH, or joint mean or how they interact. The schema titles provide basic labels such as 'Joint width (mm),' but the description adds little parameter-level meaning beyond the general notion of a rectangular tiled area.

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 uses a specific verb ('Find') and names the calculation outputs ('complete tiles per axis and remaining edge space') plus the scope ('rectangular area with internal joints only'). It is clear but does not differentiate this tool from related material-grid siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no alternatives, and no exclusions beyond the constraint 'internal joints only.' An agent gets the purpose but not the conditions under which this tool should be chosen over another grid or tile tool.

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.