Skip to main content
Glama

Black Label Real Estate Website MCP

list_products

Read-onlyIdempotent

Everything an agent can buy from Black Label Real Estate, with Stripe-verified prices, billing terms, delivery and live availability.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, open-world listing operation. The description adds useful behavioral context beyond that by disclosing Stripe-verified pricing, billing terms, delivery information, and live availability, though it does not mention authentication, pagination, or result ordering.

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?

The description is a single front-loaded sentence with no filler. Each clause adds relevant catalog, pricing, billing, delivery, or availability information.

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-parameter read-only catalog tool with annotations covering safety and no output schema, the description gives enough information about what the listing contains and how trustworthy/fresh it is. Minor operational details such as auth requirements or pagination are absent but are not central to this simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, which is the baseline for a 4 in this dimension. There are no parameter semantics to explain, and the description does not need to compensate for an input schema gap.

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 clearly identifies a catalog of purchasable products from Black Label Real Estate and lists the included information such as prices and availability. It does not explicitly distinguish itself from checkout-related siblings like create_checkout or get_checkout, so it stops short of a 5.

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 phrase 'Everything an agent can buy' implies this is the discovery step before checkout, but the description gives no explicit when-to-use guidance, exclusions, or alternative tools. Usage is implied but not operationalized.

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.

Resources