Skip to main content
Glama

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

Search Executed Chandelier Projects

search_projects
Read-only

Use when a user wants examples of completed luxury chandelier installations in mosques, royal palaces, hotels, museums, or wedding halls. Returns matching project names, categories, locations, and descriptions.

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

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword or category to search for (e.g., 'Mosque', 'Palace', 'Classic').
localeNoLanguage for search results ('en' or 'ar'). Defaults to 'en'.

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, destructiveHint=false and a closed-world scope, so the safety profile is fully covered. The description adds the result fields (names, categories, locations, descriptions), but that information is also available in the output schema. Behavior on zero matches, ranking, and result limits is not disclosed.

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, trigger condition front-loaded, then return shape. No filler, no restatement of the title, nothing to trim.

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 full schema coverage, an output schema, and complete annotations, the description only needs to convey trigger and scope, which it does. The remaining gap is minor: it does not say what happens with an empty query or when no projects match.

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%: the query parameter already documents keyword/category examples ('Mosque', 'Palace', 'Classic') and locale documents the en/ar enum and its default. The description's domain list loosely reinforces what query accepts but adds no new syntax, matching rules, or defaulting behavior, 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 names a specific resource ('completed luxury chandelier installations / executed projects') and enumerates the domains it covers (mosques, palaces, hotels, museums, wedding halls), so an agent can tell this is a keyword search over a project portfolio. It does not explicitly contrast with a sibling, but no sibling tool overlaps this purpose.

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?

'Use when a user wants examples of completed luxury chandelier installations in mosques, royal palaces, hotels, museums, or wedding halls' is a clear positive trigger condition. There are no exclusions or named alternatives, but the sibling list contains no competing search tool, so the omission is low-risk.

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.