Skip to main content
Glama

Service Request Get Tool

get-service-request
Read-only

Returns one authorized service-request inbox record using bounded status, source, urgency, and scheduling fields without exposing request descriptions, addresses, contact channels, metadata, files, or outreach controls. Use to get service request in the connected business. Returns service_request, scope.

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": {
      "service_request_id": "<service_request_id>"
    },
    "name": "get-service-request"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_request_idYesService-request ID returned by search-service-requests.

Output Schema

NameRequiredDescriptionDefault
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
service_requestYesService request data returned by the authorized safe projection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "service_request_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "service_request": {
      +      "description": "Service request data returned by the authorized safe projection.",
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "service_request",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: it explicitly lists what is redacted (descriptions, addresses, contact channels, metadata, files, outreach controls) and notes the record must be "authorized," which tells an agent what it will and will not see and hints at access scoping.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading sentence is dense and well front-loaded, but of the three sentences one is filler ("Use to get service request in the connected business") and one restates output already declared by the output schema ("Returns service_request, scope"). Roughly a third of the text 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?

An output schema exists, so return values need not be explained, and the description covers the one input's origin plus the field-visibility boundaries. What is missing is any statement of failure modes (unauthorized or not-found IDs) or routing against search-service-requests, but the definition is otherwise adequate for a single-parameter read tool.

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% and the single parameter is already documented in the schema, including that the ID comes from search-service-requests. The description mentions the bounded fields but says nothing about the required ID's format or origin, so the baseline 3 applies.

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 first sentence names a specific verb and resource ("Returns one authorized service-request inbox record") and enumerates the bounded field groups included (status, source, urgency, scheduling). The singular "one record" implicitly separates it from list/search siblings, but the follow-up sentence "Use to get service request in the connected business" is essentially a restatement of the name and adds no differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or named alternative; search-service-requests is referenced only in the schema's parameter description, not in the tool description. The only guidance is the vague "in the connected business" scoping clause, which does not tell an agent when to pick this over search-service-requests or customer-service-requests.

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