Skip to main content
Glama

Start an ELD Hub signup for a customer

start_signup
Read-onlyIdempotent

Get the tracked ELD Hub signup link, the 4 signup steps and the hand-over rules so an assistant can help a carrier register (customer enters their own card).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 and idempotentHint, so the safety profile is covered; the description then adds genuinely new behavior: the returned link is tracked, the response contains 4 signup steps plus hand-over rules, and payment is handled by the customer entering their own card rather than by the assistant.

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 front-loaded sentence with the verb and the full payload enumerated, no filler. It is dense but slightly overloaded by the parenthetical payment note, which could stand as its own short clause.

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 and no parameters, the description carries the return-shape burden and does so by listing the three things returned. What is missing is whether the link is single-use or expiring, which matters for a hand-over flow to a carrier.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the output is a fixed payload requiring no input arguments.

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?

Specific verb ("Get") plus concrete resources: the tracked ELD Hub signup link, the 4 signup steps, and the hand-over rules. That resource set clearly separates it from informational siblings like get_eld_pricing or start_trucking_business, though it never names a sibling or explicitly draws the boundary.

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 trailing clause "so an assistant can help a carrier register" implies the situation, but there is no explicit trigger condition, no when-not guidance, and no routing away from near-neighbors such as recommend_eld or check_eld_requirement.

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