Skip to main content
Glama

Little Works

discover_search

Search Discover across projects, community requests, and people for a query + place. Also returns cook/book/music/materials hints.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "discover_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional type filter: all|project|recipe|request|appointment|music
placeNoPlace slug or label, e.g. victoria-bc
queryYesSearch query

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?

No annotations are supplied, so the description carries the full burden; it does disclose a non-obvious behavioral trait — that the call returns ancillary cook/book/music/materials hints beyond the primary results. However, it says nothing about result limits, pagination, ranking, or read-only semantics, so the disclosure is partial for an unannotated tool.

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 sentences, front-loaded with the primary action and scope; no filler. The trailing hints clause is slightly jargon-heavy ('cook/book/music/materials') but is the only place that information appears.

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

Completeness3/5

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

With only 3 simple parameters, a fully-described schema, and no output schema, the definition covers the essentials but leaves gaps an agent would care about: no result-count/pagination expectations, no statement of what the 'hints' payload looks like, and an internal mismatch between 'people' and the type enum.

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?

Schema coverage is 100%, so the baseline is 3; the description adds framing by pairing 'query + place' as the search dimensions and clarifying that the search spans multiple content domains, which explains why the type/place filters matter. It does not restate the enum values, but the schema already does that adequately.

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+resource combination ('Search Discover') and names the searched domains (projects, community requests, people), which separates it from narrow siblings like search_materials. Minor imprecision: 'people' is claimed as a searchable domain but the schema's type filter has no person value, leaving the exact scope slightly fuzzy.

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 by the broad scope — the definition never says when to prefer this over discover_browse_places, discover_browse_types, or search_materials. It also gives no exclusions or preconditions (e.g., whether a place is required for place-scoped results).

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