Skip to main content
Glama

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

Get Chandelier Pricing Guidance

get_pricing_guidance
Read-only

Use when comparing showroom collections, custom palace/villa commissions, or mosque and hotel lighting tracks. Returns structured pricing packages, scope inclusions, limits, and required quote inputs.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage locale for pricing guidance ('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?

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds that the response includes scope limits and the inputs required for a quote, which is modestly useful context, but it says nothing about pricing currency, staleness, or localization behavior beyond what the schema and output schema already carry.

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: usage scenarios first, return contents second, with no filler. The scenario list is dense but each item carries distinct meaning, so nothing is wasted.

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 read-only, closed-world tool with one optional enum parameter, an output schema, and clear annotations, the description covers both selection criteria and returned content. Nothing an agent needs in order to invoke it correctly appears to be missing.

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 optional 'locale' enum is fully documented in the schema, including its 'ar' default. The description adds no meaning beyond that, so the baseline of 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 names the concrete deliverable — 'structured pricing packages, scope inclusions, limits, and required quote inputs' — for lighting/chandelier pricing, which is specific enough to distinguish it from the sibling tools (contacts, service details, site summary, resources, projects). It stops short of restating the resource domain (chandeliers) explicitly, relying on the title, but the output content makes the purpose unambiguous.

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 gives three concrete triggering scenarios: comparing showroom collections, custom palace/villa commissions, and mosque/hotel lighting tracks. That is clear when-to-use guidance. It offers no when-not-to-use or named alternative, so it falls 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.