Skip to main content
Glama

4fillment

Check product eligibility

check_product_eligibility
Read-onlyIdempotent

Says whether products are allowed, need review, or are prohibited at our warehouse. Guidance only; the binding check happens at receiving.

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": {
      "products": "<products>"
    },
    "name": "check_product_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYesProducts to check, up to 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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. Beyond that, the description discloses the three-valued outcome and the crucial caveat that the result is non-binding, which the annotations do not convey and which materially affects how an agent should act on the answer.

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?

Two short sentences with zero filler; the outcome taxonomy comes first and the advisory caveat second, which is the right order for an agent deciding whether to trust the result.

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 usefully names the possible verdicts, so an agent knows what a response can contain. It stops short of saying whether reasons or per-product breakdowns are returned and how partially-specified products are handled, but for a single read-only lookup this is close to complete.

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% and the single nested product object documents every field (description, hazmat, aerosol, lithium battery, temperature control, weight), so the schema carries the parameter burden. The description adds nothing about the products array, its 50-item cap, or which attributes influence the verdict, leaving it at the baseline.

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: it classifies products into one of three eligibility states (allowed, needs review, prohibited) for a warehouse. That is far more precise than the title's restatement, though it does not explicitly position itself against any sibling tool.

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 clause 'Guidance only; the binding check happens at receiving' implicitly tells the agent this is advisory and not an authoritative gate, which is useful context for interpreting results. However, there is no explicit when-to-use statement, no prerequisites, and no named alternative for an authoritative check.

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