Skip to main content
Glama

Lumen House

search_offers

Read-onlyIdempotent

Search current published House wares, services, marketplace references, free research and public workspace information. Returns source errors explicitly; prices are not settlement proof.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds two genuine behavioral traits beyond that: partial results surface source errors explicitly, and returned prices are not authoritative settlement proof. It stops short of describing pagination behavior or how exhaustive results are.

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 compact sentences with no preamble; the caveat about source errors and pricing is front-loaded in the second sentence. The list of content domains is somewhat padded but still within a single readable clause.

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

Completeness2/5

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

For a three-parameter search with no output schema and zero schema coverage, the description omits result shape, pagination/limit semantics and what a 'source error' looks like in the response. The pricing caveat and error disclosure are useful but leave an agent unable to predict what comes back.

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

Parameters2/5

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

Schema description coverage is 0% for limit, offset and query, and the description adds no meaning about query syntax, matching behavior, or pagination semantics. With three undocumented parameters, the low coverage demanded compensation the description does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search" is a clear verb, but the resource is described as a loose list of content domains ("House wares, services, marketplace references, free research and public workspace information") rather than stating what an 'offer' actually is. It conveys discovery over a broad corpus but never distinguishes itself from siblings such as get_offer or search_help_map.

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?

There is no when-to-use guidance and no exclusions; the agent is not told when to search versus fetching a specific offer by id or reading a guide. Usage is only implied by the verb 'search' and the presence of get_offer among siblings.

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