Skip to main content
Glama

Service Request Search Tool

search-service-requests
Read-only

Finds bounded active service-request inbox records for the authenticated business without exposing request descriptions, addresses, contact channels, or outreach controls. Use to search service requests in the connected business. Returns filters, service_requests, total, returned, 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-service-requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoClient name, service type, or request text.
viewNoInbox view; defaults to active inbox records.
limitNoMaximum number of requests to return.
statusNoOptional exact active request status.
urgencyNoOptional urgency filter.

Output Schema

NameRequiredDescriptionDefault
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
totalYesTotal for the returned result.
filtersYesFilters metadata; empty collections retain their existing JSON array representation.
returnedYesReturned for the returned result.
resolutionYesResolution metadata; empty collections retain their existing JSON array representation.
service_requestsYesBounded service requests records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "filters": {
      +      "description": "Filters metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "resolution": {
      +      "description": "Resolution metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "returned": {
      +      "description": "Returned for the returned result.",
      +      "type": "integer"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "service_requests": {
      +      "description": "Bounded service requests records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "Total for the returned result.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "filters",
      +    "service_requests",
      +    "total",
      +    "returned",
      +    "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 establish readOnlyHint and non-destructive/closed-world behavior, so the description's real contribution is the disclosure of what is deliberately withheld: descriptions, addresses, contact channels, and outreach controls are not exposed. That privacy-scoping detail plus the "bounded" limit note is meaningful context an agent cannot get from annotations.

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, front-loaded with the capability and its data-exposure constraint. The middle sentence ("Use to search service requests in the connected business") is close to redundant with the first, the one clear bit of waste.

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 search with a fully described schema and an output schema that documents filters, service_requests, total, returned, resolution, and scope, the definition covers what an agent needs. The remaining gap is routing: no statement about when this beats the singular get-service-request or customer-service-requests.

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 three of the five parameters are enums with declared defaults and bounds, so the schema carries the semantic load. The description only hints at bounds and the active-inbox default without adding syntax or interplay between q, view, status, and urgency, which is the baseline-3 outcome.

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 uses a specific verb and resource: it "Finds bounded active service-request inbox records for the authenticated business." The scope qualifiers (bounded, active, inbox) are clear, but it never names how it differs from singular siblings like get-service-request or customer-service-requests, so the distinguishing must be inferred from name alone.

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 service requests in the connected business" states an intended use but is largely a restatement of the tool name. There is no guidance on when to prefer this over get-service-request or customer-service-requests, and no stated exclusions or prerequisites, leaving usage implied rather than directed.

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