Skip to main content
Glama

GSA Fleet leasing rates

get_fleet_rates_by_sin
Read-onlyIdempotent

Returns the GSA Fleet vehicle leasing rates (monthly lease rate and rate per mile) for the vehicle type identified by its Standard Item Number (SIN), from the standard (US) or europe rate schedule, for the current fiscal year unless year is given; rates are available from fiscal year 2022. SINs are the vehicle-type codes of the GSA Fleet rate schedule; the response names the vehicle type.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rate_type": "<rate_type>",
      "sin": "<sin>"
    },
    "name": "get_fleet_rates_by_sin"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinYesStandard Item Number (SIN) identifying a GSA Fleet leased vehicle type, case insensitive.
yearNoA fiscal year starts Oct 1st, ends Sep 30th. Plan limits: Sandbox and Google add-on accounts may query dates within 30 days of today, Pro the current and previous US fiscal year, Business any date.
rate_typeYesThe GSA Fleet rate schedule: 'standard' covers vehicles leased in the United States, 'europe' covers vehicles leased in Europe.
verification_urlNoIncluded by default: a link to the official government table for the returned location and date, for the user to confirm the figures. Pass false to omit it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / year / anyOf
      Removed value: -[
      -  {
      -    "description": "A fiscal year starts Oct 1st, ends Sep 30th",
      -    "openapi_examples": {
      -      "historic": {
      -        "value": 2005
      -      },
      -      "recent": {
      -        "value": 2026
      -      }
      -    },
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / year / description
      Added value: +"A fiscal year starts Oct 1st, ends Sep 30th. Plan limits: Sandbox and Google add-on accounts may query dates within 30 days of today, Pro the current and previous US fiscal year, Business any date."
    • addedInput schema / properties / year / openapi_examples
      Added value: +{
      +  "historic": {
      +    "value": 2005
      +  },
      +  "recent": {
      +    "value": 2026
      +  }
      +}
    • addedInput schema / properties / year / type
      Added value: +"integer"
  2. Changed2 schema fields changed
    • changedInput schema / properties / verification_url / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / verification_url / description
      Previous value: -"If 'True', will include a verification url in the payload, pointing to the official government source. This is useful to crosscheck that the API returns the proper data and for auditing."New value: +"Included by default: a link to the official government table for the returned location and date, for the user to confirm the figures. Pass false to omit it."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world, so the description is not carrying the safety burden. It still adds real behavioral context beyond them: the default-to-current-fiscal-year rule, the FY2022 lower bound, and the fact that the response echoes the vehicle type name. It does not mention how an unknown SIN is handled, which would be the next useful detail.

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?

Everything is packed into one front-loaded sentence that leads with the returned values, then the key, then defaults and availability. No filler, though the semicolon-chained structure is dense enough that a reader may need a second pass.

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?

For a 4-parameter, non-nested read tool with no output schema, the description covers the essentials: what comes back (monthly lease rate, rate per mile, vehicle type name), the two required inputs, the default fiscal year, and the earliest available year. Only edge-case behavior for invalid or unavailable SINs is left unstated.

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%, so the baseline would be 3, but the description adds meaning on top: it explains that `year` defaults to the current fiscal year and that historical data starts at 2022, and it clarifies that `sin` selects a vehicle type whose name comes back in the response. The plan-limit details for `year` remain schema-only, which is appropriate.

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?

The description opens with a specific verb and resource: 'Returns the GSA Fleet vehicle leasing rates (monthly lease rate and rate per mile)' and states the key ('identified by its Standard Item Number (SIN)'). It also defines what a SIN is, so an agent can distinguish this from every sibling tool, none of which deal with fleet leasing rates.

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?

It supplies the usage context an agent needs: the default rate schedule behavior ('standard (US) or europe'), the default time window ('current fiscal year unless `year` is given'), and a hard availability floor ('rates are available from fiscal year 2022'). It does not name alternatives or exclusions, but no sibling is close enough to require routing guidance.

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.

Resources