Skip to main content
Glama

ground-motion

by com.sibfly

check_portfolio

Read-only

Batch ground-motion for many US addresses in one call. Only covered addresses are billed ($0.40 each); misses and duplicate cells are free. If credits run out mid-batch the response status is 'insufficient_credits' and unbilled items are marked — top up (buy_credits) and retry them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressesYesup to 1000 US addresses (must be an ARRAY, not one string)
max_spend_usdNohard budget cap: billing stops at this total; over-budget items come back skipped_for_budget

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
resultsNo
summaryNo
credits_remaining_usdNo

TDQS

A4.3/5.0
Behavior5/5

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

The description discloses billing behavior, credit handling, and response status details, adding significant value beyond the readOnlyHint annotation. It fully informs the agent of important behavioral traits for this operation.

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?

The description is three sentences, front-loaded with purpose, and each sentence adds value without redundancy. It is concise and well-structured.

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?

Given the presence of an output schema, the description covers billing, errors, and retry logic adequately. It does not explain return JSON structure, which is acceptable due to the output schema. Slightly more context on input validation could be helpful but not necessary.

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?

Schema coverage is 100%, but the description adds pricing context for covered addresses and explains the behavior of max_spend_usd (over-budget items marked). This provides meaningful semantic enrichment beyond the schema.

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 states it is for batch ground-motion for many US addresses, which is a specific verb and resource. It implicitly distinguishes from siblings like check_ground_motion (likely for single addresses) but does not explicitly name alternatives.

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?

The description provides clear context on when to use (for many addresses) and what to do on insufficient credits (top up and retry). It lacks explicit when-not-to-use cases but offers actionable guidance.

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