Skip to main content
Glama

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

List Public Website Resources

list_public_resources
Read-only

Use when an agent needs to enumerate all addressable Arabic and English Markdown mirrors, llms.txt files, OpenAPI schemas, and discovery URLs on alshhbaa.com. Returns a filtered list of canonical URLs.

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

Input Schema

NameRequiredDescriptionDefault
filterNoFilter resource categories ('all', 'markdown', 'api', or 'auth'). Defaults to 'all'.

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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds some behavioral context — that the result is a filtered list of canonical URLs spanning bilingual mirrors and machine-readable artifacts — but says nothing about pagination, ordering, or rate limits, which is acceptable given the output schema exists.

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 tight sentences with the usage trigger front-loaded and the return shape stated last. No filler, though the opening 'Use when an agent needs to' is slightly verbose relative to simply stating the trigger.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter read tool with annotations and an output schema, this is sufficient: the domain, the resource categories, and the return shape are all stated and nothing needed to invoke it correctly is 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 filter parameter's enum values (all, markdown, api, auth) are fully documented in the schema itself. The description's phrase 'filtered list' only alludes to the filter without adding meaning such as what 'auth' resources actually include. 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 verb ('enumerate') and a concrete, enumerated set of resources (Arabic/English Markdown mirrors, llms.txt files, OpenAPI schemas, discovery URLs) scoped to alshhbaa.com. That is far more specific than a tautology and clearly separates it from siblings like get_site_summary or search_projects, though it never explicitly contrasts itself with them.

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?

The lead phrase 'Use when an agent needs to enumerate all...' provides an implied trigger condition, but it largely restates the purpose rather than adding real decision criteria. There are no when-not conditions, no prerequisites, and no named alternatives among the siblings (e.g. when to prefer search_projects instead).

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.