Skip to main content
Glama

Alshhbaa Brassware — نحاسيات الشهباء

Get Lighting Service Details

get_service_details
Read-only

Use when a user asks specifically about Alshhbaa Brassware's Design, Supply, Installation, or Maintenance services. Returns the detailed service scope, technical coverage, and matching locale text.

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": "<service>"
    },
    "name": "get_service_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for the service details ('en' or 'ar'). Defaults to 'en'.
serviceYesThe service to inspect ('Design', 'Supply', 'Installation', or 'Maintenance').

Output Schema

NameRequiredDescriptionDefault
contentYes
structuredContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data and the description correctly adds nothing contradictory. It adds the useful detail that results are locale-dependent, but says nothing about missing services, fallbacks, or error behavior; an output schema exists, so return-format explanation is not required.

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?

Two sentences, zero waste: the usage trigger leads, the return payload follows. Nothing is repeated from the schema and no filler is present.

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?

With only two well-documented enum parameters, full annotations and an output schema, the description covers everything an agent needs to decide and invoke correctly. The only gap is that it does not mention locale as a selection consideration outside the schema, a minor omission given the annotation and schema richness.

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 both parameters are fully enumerated with defaults and the en/ar values documented in the schema itself. The description only restates the service list and the existence of locale text, adding no new syntax or constraints, 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 description gives a specific verb ('Returns'), a named resource (Alshhbaa Brassware's Design/Supply/Installation/Maintenance services) and enumerates the returned content (service scope, technical coverage, locale text). An agent can tell this is a per-service lookup rather than a catalog or pricing tool, though it never explicitly contrasts itself with the siblings.

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?

It states a clear trigger condition: 'Use when a user asks specifically about' one of the four named services, and the word 'specifically' signals the narrow scope. It does not name an alternative tool or say what to do for broader questions, which keeps it short of a 5.

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.