Skip to main content
Glama

Customer Service Requests Tool

customer-service-requests
Read-only

Lists recent active service requests associated with one authorized customer using bounded status, source, urgency, and scheduling fields. Use to inspect a customer’s service requests in the connected business. Returns customer, count, service_requests, 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": {
      "customer_id": "<customer_id>"
    },
    "name": "customer-service-requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of service requests to return.
customer_idYesCustomer ID returned by search-customers.

Output Schema

NameRequiredDescriptionDefault
countYesCount for the returned result.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
customerYesCustomer data returned by the authorized safe projection.
service_requestsYesBounded service requests records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "customer_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Count for the returned result.",
      +      "type": "integer"
      +    },
      +    "customer": {
      +      "description": "Customer data returned by the authorized safe projection.",
      +      "type": "object"
      +    },
      +    "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"
      +    }
      +  },
      +  "required": [
      +    "customer",
      +    "count",
      +    "service_requests",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, non-destructive and closed-world, so the safety profile is covered. The description adds the 'recent active' scoping and mentions 'one authorized customer', hinting at an authorization constraint, but it never explains what 'recent' or 'active' mean or how the limit bounds results. The phrase 'bounded status, source, urgency, and scheduling fields' is ambiguous since no such parameters exist, which slightly muddies rather than clarifies behavior.

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 resource and scope front-loaded; little wasted wording. The closing 'Returns customer, count, service_requests, scope' duplicates the output schema and 'in the connected business' is mild filler, keeping it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations, a fully documented two-parameter schema, and an output schema, the description covers the essentials for a simple read tool. It nonetheless leaves gaps on what 'recent active' filters, whether results are paginated under the limit, and when to prefer the sibling search 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% with only two parameters, so the schema itself documents customer_id and limit thoroughly. The description adds the notion that customer_id must reference an authorized customer found via search-customers, which is modest value, but it says nothing about the limit parameter or its default and maximum.

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 states a specific verb and resource ('Lists recent active service requests') plus a clear scope ('associated with one authorized customer'), so the agent knows exactly what it retrieves. It stops short of differentiating itself from close siblings such as search-service-requests or get-service-request, leaving the agent to infer that this is the per-customer list variant.

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 inspect a customer's service requests in the connected business' gives an implied context, but there is no when-not guidance and no named alternative for cross-customer or single-request lookups despite obvious siblings. The agent must guess that search-service-requests covers broader queries.

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