Skip to main content
Glama

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

Get Alshhbaa Brassware Site Summary

get_site_summary
Read-only

Use when you need an overview of Alshhbaa Brassware's luxury chandelier workshop, Jeddah showroom, 5-year warranty, target spaces, and public agent endpoints. Returns structured company metadata and capabilities.

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_site_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage locale for the summary ('en' or 'ar'). Defaults to 'ar'.

Output Schema

NameRequiredDescriptionDefault
contentYes
structuredContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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. The description adds only that output is 'structured company metadata and capabilities', with no note on caching, freshness, or size of the payload; the locale default is stated in the schema, not the description.

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, and no filler. The long enumerated list of covered content is slightly dense but each item conveys what the summary contains.

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 no explanation, and the description scopes the content the summary covers for a zero-required-parameter, read-only tool. The remaining gap is the absence of any guidance about when a narrower sibling tool is the better choice.

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 the single 'locale' parameter is documented with its enum values and default ('ar'), so the schema does all the work. The description contributes no additional meaning about locale, such as whether localized output changes field names or only values.

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 specific verb and resource ('overview of Alshhbaa Brassware's ... workshop, showroom, warranty, target spaces, and public agent endpoints') and says it returns structured company metadata. An agent can tell this is the site-wide profile tool rather than a per-resource lookup like get_contact_channels or search_projects, though it never names those siblings explicitly.

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 when you need an overview of...' gives an implied trigger condition, which is better than nothing. However, it offers no when-not guidance and no routing to the sibling tools for narrower needs (contacts, pricing, services, resources), so the agent must infer the boundary itself.

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.