Skip to main content
Glama

Specify foam for a cushion or pad

specify_foam
Read-only

Give the right foam specification for a job: density in kg/m3, hardness in newtons, depth in mm, foam type, wadding wrap, and the UK fire requirement. Use whenever someone asks what foam to buy, how thick, how firm, or why their cushions went flat. Density and hardness are different things and people constantly confuse them: density is how long it lasts, hardness is how it feels. This tool keeps them apart.

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": {
      "application": "<application>"
    },
    "name": "specify_foam"
  }
}

Input Schema

NameRequiredDescriptionDefault
depth_cmNoOptional. Cushion front-to-back measurement.
width_cmNoOptional. Cushion width, for a cut size.
applicationYesWhat the foam is for. Options: sofa seat, sofa back, dining seat, headboard, bench, footstool, mattress, outdoor, contract seat
thickness_mmNoOptional. Override the recommended thickness.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing what the tool returns (a full spec including fire requirement) and by clarifying the density-vs-hardness distinction, which is behavioral context not present in the annotations.

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 and usage triggers are front-loaded in the first two sentences. The closing density-vs-hardness aside is slightly digressive but earns its place by pre-empting a common user confusion.

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, the description carries the burden of explaining return values, and it does so by listing the spec components. For a single-required-parameter read-only tool, this is nearly complete; only the exact response shape is left implicit.

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 description coverage is 100%, so all four parameters are already documented, and the description adds no syntax or format detail for application, depth, width, or thickness. The density/hardness explanation is conceptual rather than parameter-level, 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 ('Give the right foam specification for a job') and enumerates the outputs (density, hardness, depth, foam type, wadding wrap, fire requirement). It is clearly distinct from the sibling calculators, though it never names an alternative to route against.

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?

It gives concrete trigger phrases: 'Use whenever someone asks what foam to buy, how thick, how firm, or why their cushions went flat.' That is clear when-to-use context, but there are no exclusions or explicit pointers to sibling tools like check_fire_regulations.

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