Skip to main content
Glama

Pinpoint dealership sales tools

by io.github.benian-technologies
OverviewDiscussionsAdmin

Call recording consent by state

call_recording_consent
Read-only

Whether one party or every party must consent before a phone call is recorded in a US state, the statute, a note for sales teams, and the greeting, outbound and text notices to use on your calls. All 50 states and DC. General information, not legal advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repNoRep first name for the outbound notice
stateYesState name or two-letter abbreviation, for example "FL" or "Florida"
companyNoYour company name for the notices

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
+  "description": "Your company name for the notices",
+  "type": "string"
+}
    • removedInput schema / properties / dealership
      Removed value: -{
-  "description": "Dealership name for the notices",
-  "type": "string"
-}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark this read-only and closed-world; the description adds useful behavioral context by listing what the lookup returns and by adding a trust disclaimer ('General information, not legal advice'). It also confirms the closed scope ('All 50 states and DC') without contradicting any annotation.

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 packs the core purpose and output contents into a single front-loaded sentence, followed by two short scope/disclaimer sentences. It is compact and every clause adds information.

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 3-param, no-output-schema read tool, the description tells the agent what content to expect (consent rule, statute, sales note, notices), the coverage scope, and a caveat. It could be more explicit about optionality of rep/company, but the schema already covers that.

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 description coverage is 100%, and the schema already explains state, rep, and company. The description does not add meaning beyond the schema, so the baseline of 3 is appropriate.

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 identifies the resource—US state call-recording consent rules—and enumerates the returned content (statute, sales note, notices). It lacks an explicit verb and doesn't name a sibling for differentiation, but the title and scope ('All 50 states and DC') make the function unmistakable.

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?

It implies the tool is for sales teams needing state-specific consent rules and ready-to-use greeting/outbound/text notices, and it cautions that it is general info rather than legal advice. It does not explicitly state when to prefer this over siblings like answer_recording_question or ai_caller_disclosure.

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

All Pinpoint dealership sales tools 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