Skip to main content
Glama

ground-motion

by com.sibfly

get_motion_history

Read-only

Multi-year cumulative motion history for an address. Pass from_date and to_date (YYYY-MM-DD) to get the movement between two dates. Costs $0.40 (misses free). dry_run=true is a FREE preview (points + dates + cost, no data); max_age_days returns free instead of billing for stale data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNo
lonNo
addressNo
dry_runNoFREE preview: coverage + n_points + would_cost, no series, no charge
to_dateNo
from_dateNo
max_age_daysNoif data older than this, return free instead of billing

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
datesNo
deltaNo
cum_mmNo
statusNo
cost_usdNo
credits_remaining_usdNo

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true. The description adds cost details ($0.40, free for misses), free preview via dry_run, and free return for stale data via max_age_days. This goes beyond annotations but lacks details on behavior when location parameters are ambiguous.

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?

Three sentences, front-loaded with purpose, each sentence adds distinct value (date range, cost, free preview). No filler or redundancy.

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

Completeness3/5

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

Covers core functionality, cost, and free options well. However, with 7 parameters (0 required) and low schema coverage, the description leaves ambiguity about location parameter interplay. Output schema exists so return format is not required, but location handling is missing.

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 only 29%. The description adds date format (YYYY-MM-DD) and clarifies dry_run and max_age_days, but does not explain lat/lon/address usage or dependency. With low coverage, more compensation was needed.

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?

The description clearly states the tool retrieves multi-year cumulative motion history for an address over a date range. It specifies the resource ('motion history') and action ('get') and distinguishes from sibling tools like check_ground_motion by focusing on cumulative history.

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?

Provides guidance on parameters (from_date, to_date format, dry_run for free preview, max_age_days for stale data) and cost implications. However, it does not explicitly state when to use this tool versus alternatives like check_ground_motion.

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

All ground-motion toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct function: account management, ground motion queries, batch processing, history, and Q&A. No two tools serve overlapping purposes, and descriptions clearly differentiate them.

Naming Consistency4/5

Most tools use a 'verb_noun' pattern with verbs like get, register, buy, check, ask. However, 'check' is used for two tools (check_ground_motion, check_portfolio) while similar retrieval tools use 'get' (get_motion_history), creating a slight inconsistency in verb choice.

Tool Count5/5

With 9 tools, the server covers account setup, credit management, ground motion queries (single, batch, history), and follow-up Q&A—a well-scoped set that earns each tool's place.

Completeness5/5

The tool surface covers the full lifecycle: account creation (register_agent), credit purchasing (buy_credits), balance/usage (get_account, get_usage), coverage checks (get_coverage), ground motion queries (check_ground_motion, check_portfolio), motion history (get_motion_history), and post-purchase Q&A (ask_inspector). No obvious gaps.

Resources