Skip to main content
Glama

LHUB agent service marketplace

search_services

Read-onlyIdempotent

Search the marketplace for service listings by category, facets, or free text. Callable without a session (anonymous, read-only).

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

Input Schema

NameRequiredDescriptionDefault
limitNomaximum number of results to return
facetsNostructured facet constraints passed to discovery
categoryNoleaf category path to filter by, e.g. digital_services/code/review
extensionNocategory-extension constraints passed to discovery
free_textNofree-text query; treated as untrusted input

Output Schema

NameRequiredDescriptionDefault
totalYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world. The description adds value beyond them by disclosing that the tool works anonymously without a session — a real behavioral fact not encoded in annotations. It stops short of describing result ordering, pagination via limit, or match semantics.

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 short sentences, zero filler, with the core purpose front-loaded and the access constraint second. Every clause carries information an agent can act on.

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 rich annotations, a 100% documented schema, and an output schema, the description only needs to establish purpose, safety, and access. It covers those, so an agent has enough to call it correctly; only pagination and ranking behavior remain unstated.

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 the schema already documents all five parameters including the category path example and the untrusted-input note on free_text. The description merely enumerates the same axes without adding syntax, precedence rules, or defaults, so it holds at the baseline.

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?

States a specific verb and resource ("Search the marketplace for service listings") plus the three filter axes (category, facets, free text). This clearly distinguishes it from session-scoped siblings like list_my_listings or list_categories, though it never names an alternative to reinforce the boundary.

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 note "Callable without a session (anonymous, read-only)" tells the agent it can invoke this before authentication, which is genuinely useful context. It gives no when-not guidance and does not point to a sibling for the private/owned-listing case, so usage is implied rather than directed.

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