get_flip_score
Read-only
GovAuctions Flip Score resale signal for a live GSA listing (valued against the full-market comp archive): estimated value, effective bid, and discount.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
govauctions.app
TDQS
B3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds context about valuation against a comp archive, which is useful but not extensive. No behavioral pitfalls or additional constraints are disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that efficiently conveys the purpose and outputs. It is front-loaded and contains no redundant information.
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?
Given low complexity (1 param, no nested schemas) and annotations that cover safety, the description provides enough context for basic use. However, it lacks details on output structure or format, which would be helpful for an agent processing the response.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage for the single parameter 'id', and the description does not explicitly describe the parameter. The mention of 'live GSA listing' hints that id is a listing ID, but this is implicit and insufficient for an agent to understand expected format or source.
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 it provides a 'Flip Score resale signal' for a live GSA listing, listing outputs: estimated value, effective bid, and discount. It implicitly distinguishes from siblings (get_listing, get_sold_comps, search_listings) by focusing on this specific metric.
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 explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, limitations, or scenarios where other tools would be preferable.
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.9/5.0
Disambiguation4/5
Most tools have distinct purposes: search_listings and get_listing differ by lookup method, and get_sold_comps, get_sold_history, and get_price_trend are clearly separated by whether they provide aggregate percentiles, individual sales, or monthly trends. The only minor ambiguity is between get_sold_comps and get_price_trend, both derived from the same comps, but their descriptions make the difference in output format clear.
Naming Consistency5/5
All tool names follow the consistent verb_noun pattern using lowercase snake_case: get_* for data retrieval and search_listings for searching. There are no mixed conventions or style inconsistencies, making the naming highly predictable.
Tool Count5/5
With 8 tools, the server is well-scoped for its purpose of querying government auction listings and pricing data. Each tool covers a distinct functional need without redundancy, and the count is squarely in the ideal range for a domain-specific API.
Completeness4/5
The tool surface covers the core read-only workflows: searching and retrieving listings, getting sold-price comps, viewing historical sales, examining price trends, estimating flip value, and checking data coverage. A minor gap is the lack of explicit category or market listing endpoints, but agents can work around this via search_listings and get_comp_coverage.