Skip to main content
Glama

Lumen House

search_help_map

Read-onlyIdempotent

Search free, curated public research by substring and optional topic. Preserve provenance, stale flags, rights and sample limitations. These are not verified jobs or buyer demand.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
topicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 genuinely new behavioral context by warning that records carry provenance, stale flags, rights and sample limitations that must be preserved, and that results are not verified demand. It omits anything about result volume, the 20-item cap, or ordering.

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?

Three short sentences, front-loaded with the verb and scope, with zero filler. The second sentence is a compressed fragment ('Preserve provenance, stale flags, rights and sample limitations') that reads more like a terse reminder than prose, but it still earns its place by flagging data caveats.

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 no output schema and only three simple parameters, the description supplies most of what an agent needs: what is searched, how matching works, what the records contain, and what they are not. The remaining gap is operational detail around the limit parameter and result-set size, which is minor for a read-only search.

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 0%, so the description carries the burden, and it only partly does: 'by substring' clarifies how the query parameter matches, and 'optional topic' signals that topic is not required. The limit parameter is never mentioned, nor is the maximum of 20 or the meaning of the topic enum values, which remain undocumented in both places.

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 gives a specific verb and resource — 'Search free, curated public research' — plus the matching mode ('by substring') and an optional facet ('topic'). It also draws a boundary against adjacent concepts ('not verified jobs or buyer demand'), which helps separate it from search_offers, though it never names that sibling explicitly.

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?

Usage is only implied: the reader infers you call this to look up research entries rather than offers or jobs. There is no explicit statement of when to prefer this over get_help_map_item (single-item lookup) or search_offers, and no prerequisites or exclusion conditions beyond the negative framing about jobs/demand.

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