Skip to main content
Glama

ground-motion

by com.sibfly

ask_inspector

Read-only

FREE follow-up Q&A with the SibFly Inspector about a report you ALREADY BOUGHT (buy via check_ground_motion first). Ask what the numbers mean for foundations, staleness, seasonal swings, etc. It answers only from the report's numbers (never invents), and won't give buy/walk-away advice. Per-account message allowance applies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesthe address of a report already purchased on this account
questionYesyour question about the report

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
replyNo

TDQS

A4.7/5.0
Behavior5/5

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

Description adds significant behavioral context beyond annotations: it's free, answers only from report numbers, never invents info, and won't give investment advice. Annotations only provide readOnlyHint, so the description provides essential behavioral disclosure.

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 with key info front-loaded: FREE, follow-up, prerequisite. Every sentence adds value with no waste.

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?

Given tool complexity (simple Q&A) and existence of output schema, the description adequately covers input constraints, expected behavior, and limitations (no invention, no advice). It is complete for an agent to use correctly.

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 coverage is 100% with both parameters described. The description reinforces the context (address must be for a bought report) but doesn't add syntax or format details beyond the schema. Baseline 3 is appropriate given high schema coverage.

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?

Description clearly states it's a follow-up Q&A tool for reports already bought via check_ground_motion. It specifies the exact resource (report) and action (asking questions), and distinguishes from siblings like check_ground_motion (buy) and other unrelated tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (after buying a report via check_ground_motion) and when not to use (no buy/walk-away advice). Also mentions per-account message allowance, setting clear usage boundaries.

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