Skip to main content
Glama
Sign In

mcp

by com.precision-concretecoating
OverviewDiscussionsAdmin

Next best intake question

get_next_estimate_question
Read-onlyIdempotent

Returns the single highest-value question still unanswered, in natural language, along with why it matters. Ask one question at a time and send the answer back through update_estimate_request.

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": {
      "request_id": "<request_id>",
      "customer_access_token": "<customer_access_token>"
    },
    "name": "get_next_estimate_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesThe request_id returned by create_estimate_request.
customer_access_tokenYesThe one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about the return format (question and why it matters) but no additional behavioral traits beyond what annotations provide. No contradiction.

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 two sentences long, front-loaded with the core purpose, and contains no wasted words. It efficiently communicates what the tool does and how to use it.

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 read-only tool with complete schema coverage and rich annotations, the description provides essential return info and workflow context. A minor gap is not specifying behavior when no questions remain (e.g., returns null), but overall it is sufficiently complete.

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%, with both parameters fully described. The description does not add further meaning to the parameters beyond what is already in the schema, so the baseline score of 3 applies.

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 returns 'the single highest-value question still unanswered, in natural language, along with why it matters.' This is a specific verb+resource (returns a question) that distinguishes it from sibling tools like 'update_estimate_request' which sends answers.

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?

The description gives explicit workflow guidance: 'Ask one question at a time and send the answer back through update_estimate_request.' This tells the agent when to use this tool (to get the next question) and how to continue the interaction, though it does not explicitly mention alternatives or exclusions.

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

All mcp 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