get_stats
Get database statistics and distributions
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
resale
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose behavior. It simply says 'Get', implying a read operation, but lacks details on safety (e.g., read-only), rate limits, or any side effects.
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 a single, concise sentence with no unnecessary words. It is appropriately front-loaded and delivers the core purpose efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description is too minimal. It doesn't explain what statistics are returned, the format, or how they can be used, leaving the agent with significant ambiguity.
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?
There are no parameters, and schema coverage is 100%. According to guidelines, zero parameters baselines at 4, and the description does not need to add parameter meaning.
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 clearly states the tool retrieves 'database statistics and distributions', which is a distinct purpose from sibling tools that focus on specific entities like listings or resorts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The sibling tools cover specific domains, but the description does not clarify that this tool is for overall database metrics.
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.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a distinct data source or action: search tools query different databases (listings, complaints, FL DBPR projects), get tools retrieve specific entities (listing, resort, payment history), list tools aggregate brands/resorts, and bridge tools handle curation. There is no overlap in purpose.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in lowercase snake_case: add_to_bridge, create_bridge, get_listing, get_orientation, get_payment_history, get_resort, get_stats, list_brands, list_resorts, search_complaints, search_dbpr_projects, search_timeshares. The pattern is predictable and clear.
Tool Count5/5
With 12 tools, the server is well-scoped for a timeshare research and bridge curation domain. It covers multiple data sources (listings, complaints, FL DBPR, stats) and actions (search, get, list, create, add) without being excessive or too sparse.
Completeness4/5
The tool set covers core workflows: orientation, searching, viewing details, complaints, registration, and bridge creation. Minor gaps exist: there is no tool to remove listings from bridges or to list existing bridges, and no update/delete for listings (though likely out of scope). Overall, the surface is largely complete for the intended use.