Skip to main content
Glama

Check supplier project coverage and questions

get_supplier_questions
Read-onlyIdempotent

Start here for a material supplier deadline. Check live supplier-events-v3 coverage for any US state or DC, project type, and hiring relationship. Returns supported, review_required, or no_lien_right with a reason, applicable event questions, date policies, sources, and exact rule and question identities. It may also return recurring_notice_intake and short-form guidance. Confirm ordinary answers against the project facts. Requires a customer key. Discovery needs no delivery dates and uses no calculation allowance. A 503 means the reviewed source is unavailable.

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": {
      "state": "<state>",
      "project_type": "<project_type>",
      "hired_by": "<hired_by>",
      "context": "<context>"
    },
    "name": "get_supplier_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesProject jurisdiction: state or DC.
contextYesFor anonymous analytics, use one of these exact goals. Determine supplier notice and lien deadlines / Identify which facts a supplier calculation needs / Read a state's lien guide / Browse available lien guides. Leave empty if none fits. Keep personal and project information out of this field.
hired_byYesWho ordered the materials from the supplier: the owner, a contractor, or a subcontractor.
project_typeYesConstruction project type: private commercial, private residential, or public.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / hired_by / description
      Added value: +"Who ordered the materials from the supplier: the owner, a contractor, or a subcontractor."
    • addedInput schema / properties / project_type / description
      Added value: +"Construction project type: private commercial, private residential, or public."
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "For anonymous analytics, use one of these exact goals. Determine supplier notice and lien deadlines / Identify which facts a supplier calculation needs / Read a state's lien guide / Browse available lien guides. Leave empty if none fits. Keep personal and project information out of this field.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "state",
      -  "project_type",
      -  "hired_by"
      -]New value: +[
      +  "state",
      +  "project_type",
      +  "hired_by",
      +  "context"
      +]
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the customer-key requirement, the enumerated result states (supported / review_required / no_lien_right) with reasons, the extra possible payloads (recurring_notice_intake, short-form guidance), and the meaning of a 503 (reviewed source unavailable). The annotations already cover read-only and idempotency, so this added auth, error, and result-shape context is what earns credit here; it does not contradict them.

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?

Front-loaded with the action and entry-point cue, then layered with result states and constraints in short sentences with almost no filler. A few clauses ("Confirm ordinary answers against the project facts") are terse to the point of ambiguity, keeping it from being maximally clean.

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?

With no output schema present, the description usefully enumerates the return shape (status, reason, questions, date policies, sources, identities) and the auth prerequisite. Complete enough to call correctly for a four-required-parameter read tool, with only the analytics `context` parameter left unexplained in prose.

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 is 100% with per-parameter descriptions and two enums, so the schema carries the parameter burden. The description only reinforces that state allows any US state or DC and that project type and hiring relationship are the other axes, adding little syntax or meaning beyond the schema, and it never mentions the analytics-only `context` field.

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?

States a specific verb and resource ("Check live supplier-events-v3 coverage") scoped to state/DC, project type, and hiring relationship, plus an explicit entry-point instruction ("Start here for a material supplier deadline"). This makes it distinguishable from the calculate_* siblings, which the note about dates and calculation allowance further separates it from, without naming them.

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?

"Start here" plus "Discovery needs no delivery dates and uses no calculation allowance" gives clear when-to-use context and implicitly steers agents toward a calculation tool afterwards. It lacks an explicit "do not use this for X" exclusion, so it stops short of a full routing statement.

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.