Skip to main content
Glama

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

Get Showroom Contacts & Hours

get_contact_channels
Read-only

Use when a user asks how to visit, call, email, or message Alshhbaa Brassware in Jeddah. Returns verified email, showroom addresses, Google Maps links, social profiles, and operating hours.

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": "get_contact_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage locale for showroom details ('en' or 'ar'). Defaults to 'ar'.

Output Schema

NameRequiredDescriptionDefault
contentYes
structuredContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered by structured data. The description adds the useful qualifier that the data is 'verified' and pins it to a single physical location in Jeddah, but it says nothing about freshness, caching, or what happens if a channel is unavailable. Given a full output schema, the enumeration of return fields is largely redundant.

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?

Two sentences, front-loaded with the trigger condition before the payload description, with no filler or hedging. The second sentence partially duplicates what the output schema already declares, which is the only inefficiency.

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 zero-required-parameter, closed-world read tool with full annotation coverage and an output schema, the description supplies everything needed to decide to call it and what to expect. The one meaningful gap is silence on locale behavior, which an agent would only learn from the schema.

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%: the single 'locale' parameter is documented with its enum values and default ('ar') in the schema itself. The description adds no information about the locale parameter—not even that the tool returns Arabic by default—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?

States a concrete verb and resource ('Returns verified email, showroom addresses, Google Maps links, social profiles, and operating hours') and ties it to a business entity (Alshhbaa Brassware in Jeddah). An agent can distinguish this contact/hours lookup from siblings like get_pricing_guidance or get_service_details, though the description never names an alternative to sharpen the boundary.

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?

The leading 'Use when a user asks how to visit, call, email, or message...' gives a clear, concrete trigger condition covering several phrasings a user might use. It stops short of stating when NOT to use it or which sibling to pick for adjacent questions (e.g., hours vs. service details), so it earns a 4 rather than 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.