Skip to main content
Glama

Search Quotes Tool

search-quotes
Read-only

Searches authorized estimates using bounded customer, status, title, and total fields; notes, terms, and addresses are excluded. Use to search quotes in the connected business. Returns query, count, total, quotes, resolution, scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search-quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of estimates to return.
queryNoEstimate title, customer name, email, or phone.
statusNoOptional estimate status.
customer_idNoRestrict results to one customer ID.

Output Schema

NameRequiredDescriptionDefault
countYesCount for the returned result.
queryYesQuery used or returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
totalYesTotal for the returned result.
quotesYesBounded quotes records returned by this tool.
resolutionYesResolution metadata; empty collections retain their existing JSON array representation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Count for the returned result.",
      +      "type": "integer"
      +    },
      +    "query": {
      +      "description": "Query used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "quotes": {
      +      "description": "Bounded quotes records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "resolution": {
      +      "description": "Resolution metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "total": {
      +      "description": "Total for the returned result.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "query",
      +    "count",
      +    "total",
      +    "quotes",
      +    "resolution",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  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 cover safety (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description's real contribution is the authorization boundary ('authorized estimates') and the explicit statement that notes, terms, and addresses are excluded from matching. That exclusion is genuinely useful behavioral context an agent could not get from the schema.

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?

Three short sentences with the scope and exclusions front-loaded; nothing is padded. The trailing return-field list ('query, count, total, quotes, resolution, scope') is largely redundant given the output schema and is the one part that does not earn its place.

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 read-only, four-parameter search tool with full schema coverage and an output schema, the description covers scope, exclusions, and the authorization boundary. Remaining gaps are minor: no mention of default result size or that limit is capped at 20.

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%, so the schema already defines all four parameters, and the description adds only a summary of searchable fields. It also mentions 'total' as a bounded field, which does not correspond to any parameter and can mislead an agent into trying to filter on it.

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?

States a specific verb and resource ('Searches authorized estimates') and scopes the searchable fields, which lets an agent distinguish it from get-quote and the other search-* siblings. The only friction is the quote/estimate terminology swap, which is inferable but not stated explicitly.

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?

'Use to search quotes in the connected business' gives only a broad implied context. There is no statement of when to prefer this over get-quote for a single record, nor any exclusion or prerequisite beyond 'authorized'.

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