Skip to main content
Glama

get_furniture_catalog

Buy mode furniture and décor catalog with prices in ₦ (static list synced from the game client). Optional category or max price filter.

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

Input Schema

NameRequiredDescriptionDefault
furniture_categoryNoOptional category filter (comfort, sleep, kitchen, power, …).
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
furniture_max_price_ngnNoOptional max item price in in-game naira.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden, and it does add one genuinely useful fact: the list is static and synced from the game client, so data may lag. It stops short of covering staleness/sync cadence, whether pagination or ordering applies, or read-only safety semantics.

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 short clauses with the core identity front-loaded and no filler. The trailing fragment about optional filters is terse and slightly clipped, but overall it is efficient rather than under-specified.

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-required-parameter read tool with full schema coverage and no output schema, the description covers what the tool is and that filtering is optional. Missing only sibling disambiguation and any hint of result size/ordering.

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%, so all three parameters are already documented, and the description merely echoes the two filters (category, max price) and omits notification_message entirely. Baseline 3 applies since the schema does the heavy lifting.

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 states a specific verb and resource (furniture/décor catalog) plus a distinguishing property: prices in ₦ and a static list synced from the game client. It does not, however, differentiate itself from the sibling get_home_catalog, leaving the agent to infer why two catalog tools exist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is that filtering is optional, which tells the agent nothing about when to reach for this tool versus get_home_catalog, apply_home_design, or preview_home_design. No exclusions, prerequisites, or alternatives are named.

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