Skip to main content
Glama
Sign In

Ca Dmv

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ca Dmv Insurance Lookup

ca_dmv_insurance_lookup
Read-onlyIdempotent

Look up an auto insurer's five-digit NAIC code from the California DMV insurance-carrier list by company name. California requires the NAIC number when reporting insurance for a registered vehicle, so this answers "NAIC code for State Farm", "what is Geico's NAIC number", or "insurer codes matching Progressive". The list is California's; NAIC codes themselves are national.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "insurer": "State Farm"
    },
    "name": "ca_dmv_insurance_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
insurerYesInsurance company name or fragment, e.g. "State Farm", "Geico", "Progressive".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, providing a clear safety profile. The description adds minimal behavioral context (e.g., that codes are national) but does not disclose additional traits like error handling or data source freshness.

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 concise: three sentences that start with the core purpose, then provide usage examples and a clarifying note. Every sentence adds value with no redundancy.

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 simple lookup tool with one parameter and no output schema, the description covers the use case, data source, and typical queries. It could mention the return format explicitly but is adequate for agent understanding.

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

Parameters3/5

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

Schema coverage for the single parameter 'insurer' is 100%, with a clear description. The description reinforces the parameter usage with examples but adds no new semantic details beyond the schema.

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 clearly states the tool's function: look up an auto insurer's NAIC code from the California DMV list by company name. It provides example queries and distinguishes from siblings like ca_dmv_driver_licenses by focusing on insurance codes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when needing an NAIC code for California DMV reporting, but does not explicitly state when not to use it or compare with other tools. No alternatives among siblings are mentioned.

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

All Ca Dmv toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources