Skip to main content
Glama

4fillment

Service overview

get_service_overview
Read-onlyIdempotent

What 4fillment does: warehouses, services, service levels, product rules, and how sign-up works.

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

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?

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description contributes only content scope (which topics come back), with no statement about response size, whether the content is static documentation, or freshness.

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?

A single short clause with no filler; the content list is front-loaded and every item earns its place. It is a sentence fragment rather than a complete sentence, which slightly weakens the framing but costs no length.

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?

For a zero-parameter read with annotations carrying the safety profile and no output schema, the description needs only to convey what comes back, and it does so by enumerating the covered topics. Only a note on whether the response is static reference material or live config would add more.

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; there is nothing for the description to disambiguate. The listed topic areas do, however, help set expectations for what the parameterless call returns.

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 enumerates the concrete subject matter the tool returns: warehouses, services, service levels, product rules, and sign-up flow. That is enough to distinguish a general orientation read from resource-specific siblings like get_case or get_rate_card, though it never states a verb or explicitly frames itself as an overview lookup.

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: an agent can infer this is the onboarding/orientation call to make before asking about specific cases or rate cards. There is no explicit 'use this when...' statement and no mention of when a sibling like ask_4fillment would be preferred.

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