Skip to main content
Glama

iMoving - moving quotes

Get a mover's profile

get_mover
Read-onlyIdempotent

Gets a moving company's profile from iMoving: where it is based, years in business, moves done, its rating (1-10) and its most recent customer reviews (1-5 stars each). Use the mover_id of an offer from get_moving_quote.

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": {
      "mover_id": "<mover_id>"
    },
    "name": "get_mover"
  }
}

Input Schema

NameRequiredDescriptionDefault
mover_idYesmover_id of an offer from get_moving_quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: what fields come back and, importantly, the scale of each metric (rating 1-10, reviews 1-5 stars), which an agent needs to interpret results. It doesn't say how many reviews 'most recent' means or how it behaves for an unknown or invalid mover_id.

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 sentences, zero padding, and the value proposition (the profile fields) is front-loaded ahead of the usage note. Everything in it is actionable for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only lookup with full annotation coverage and no output schema, the description is complete: it covers what is fetched, how the returned metrics are scaled, and how to obtain the required ID. No gap an agent would need to call it correctly remains open.

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?

With one parameter at 100% schema description coverage, the schema already carries the meaning, and the description's 'mover_id of an offer from get_moving_quote' essentially restates the schema's own parameter text. It adds provenance context but no new detail such as ID format, validity ranges, or error behavior on a stale ID. Baseline 3 is appropriate here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb ('Gets') plus a specific resource ('a moving company's profile from iMoving'), and it enumerates the returned content: location, years in business, moves done, rating on a 1-10 scale, and recent reviews on a 1-5 scale. That detail makes it trivially distinguishable from get_moving_quote and list_move_sizes without opening either schema.

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?

Explicitly states the prerequisite context: call it with the mover_id of an offer obtained from get_moving_quote, which tells the agent where this tool sits in the workflow. It stops short of any when-not guidance (for example, what to do if the mover_id came from elsewhere), so it's clear context rather than full routing guidance.

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