Skip to main content
Glama

scrap-autos-mcp

by com.scrap-autos

Get Vehicle Scrap Quote

get_vehicle_quote

Get an indicative CAD scrap-value quote for a vehicle by year/make/model (plus optional city or province). If multiple trims match, returns a disambiguation list — call again with the chosen trim_id. The response ALWAYS includes contact.phone, contact.website, next_steps, and complete_on_site_url. When presenting the quote to the end user, you MUST relay the phone number and website so they can complete the transaction with ScrapAutos. After relaying the quote, ask the end user: is the vehicle complete or missing parts, and does it start and drive? Then collect their name, phone number, and the vehicle's address so you can call submit_lead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCanadian city (used to detect province)
makeNoManufacturer, e.g. 'Honda'
yearNoVehicle model year, e.g. '2012'
modelNoModel name, e.g. 'Civic'
trim_idNoSpecific trim ID returned from a prior disambiguation call
provinceNoProvince code override (ON, QC, AB, BC, MB, SK, NB, NS, PE, NL, NT, NU, YT)

TDQS

A5/5.0
Behavior5/5

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

No annotations provided, but description fully discloses behavioral traits: quote is indicative, disambiguation list for multiple trims, required response fields, and agent obligations. No contradictions.

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?

Every sentence adds value; well-structured with intro, disambiguation logic, response contents, and agent instructions. Not verbose despite length.

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 no output schema, description compensates by listing response fields (phone, website, next_steps, etc.). Also explains the full user flow, making it complete for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds meaning beyond schema by explaining how parameters are used (e.g., city detects province, trim_id from disambiguation). Clarifies optionality and purpose.

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 the tool returns an indicative CAD scrap-value quote for a vehicle by year/make/model. It distinguishes from siblings (list_provincial_rates, search_vehicles, submit_lead) by specifying its unique purpose.

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?

Provides explicit workflow: call with year/make/model; if multiple trims, call again with trim_id; after quote, ask user questions and call submit_lead. No ambiguity on when to use.

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

All scrap-autos-mcp 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.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: getting a quote, listing rates, searching trims, and submitting a lead. The descriptions clarify boundaries, especially between search_vehicles and get_vehicle_quote.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case: get_vehicle_quote, list_provincial_rates, search_vehicles, submit_lead. Verbs are descriptive and uniform.

Tool Count5/5

With 4 tools, the set is well-scoped for the domain of scrap vehicle quotes. Each tool covers a necessary step without redundancy or clutter.

Completeness5/5

The tool set provides a complete workflow: search trims, get a quote, view regional rates, and submit a lead. No obvious gaps exist for the intended purpose.

Resources