Skip to main content
Glama
Sign In
nexusfeed-mcp

nexusfeed-mcp

by NexusFeed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ltl_get_accessorials

Retrieve current LTL carrier accessorial fees including liftgate, residential delivery, re-delivery, inside delivery, limited access, notification, and appointment fees. Input carriers or fee types to get schedules.

Instructions

[COMING SOON] Returns the current accessorial fee schedule for LTL carriers — liftgate, residential delivery, re-delivery, inside delivery, limited access, notification, appointment fees, and more. This tool is not yet available and will return an unavailability message. Use ltl_get_fuel_surcharge for current carrier data.

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

Input Schema

NameRequiredDescriptionDefault
carriersNo
fee_typesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

No annotations are present, so the description bears full responsibility. It discloses that the tool is not yet available and will return an unavailability message, which is important behavioral context. No other traits like auth or side effects are mentioned, but the core constraint is clearly stated.

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 description is brief with two major sentences plus the coming-soon tag. It front-loads the purpose. While concise, the '[COMING SOON]' marker could be placed after the description for better flow. Overall, no wasted words.

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 not-yet-available tool with an output schema, the description adequately explains its intended function, current unavailability, and directs to a sibling alternative. It lacks parameter details and output content hints, but given the 'coming soon' status, the context is sufficiently complete.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description provides no explanation of the two parameters (carriers and fee_types). It does not clarify allowed values, formats, or how they influence the output, leaving the agent without meaningful guidance beyond the schema's type information.

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 clearly states the tool returns the current accessorial fee schedule for LTL carriers, listing examples like liftgate and residential delivery. It distinguishes from sibling tool ltl_get_fuel_surcharge. However, the '[COMING SOON]' prefix may temporarily confuse about availability.

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 description advises 'Use ltl_get_fuel_surcharge for current carrier data', providing a specific alternative. It implies this tool is for accessorials but does not explicitly state when to use it over other tools or that it is currently unavailable for actual queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools