Skip to main content
Glama

Search concepts

search_concepts
Read-only

Search the product knowledge vault by free-text query. Useful when you need product knowledge but don't yet know which concept ids exist. Returns ranked hits (id, title, type, score, snippet) only; get_concept returns one full note and get_context an assembled briefing. An empty hit list means nothing matched.

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": "search_concepts"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoSearch mode. "hybrid" (default) fuses keyword and semantic ranking; semantic silently falls back to keyword if embeddings are unavailable.hybrid
tagsNoOnly return concepts carrying ALL of these tags.
typeNoOnly return concepts of this type.
limitNoMax hits to return (default 10).
queryYesFree-text search query, e.g. "lead scoring" or "session auth".
productNoOnly return concepts belonging to this product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "concept",
      -  "domain",
      -  "feature",
      -  "story",
      -  "spec",
      -  "workflow",
      -  "task",
      -  "decision",
      -  "constraint",
      -  "pattern",
      -  "glossary",
      -  "iteration",
      -  "milestone"
      -]New value: +[
      +  "concept",
      +  "domain",
      +  "feature",
      +  "story",
      +  "spec",
      +  "workflow",
      +  "task",
      +  "decision",
      +  "constraint",
      +  "pattern",
      +  "glossary",
      +  "iteration",
      +  "milestone",
      +  "epic"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "concept",
      -  "domain",
      -  "feature",
      -  "story",
      -  "spec",
      -  "workflow",
      -  "task",
      -  "decision",
      -  "constraint",
      -  "pattern",
      -  "glossary"
      -]New value: +[
      +  "concept",
      +  "domain",
      +  "feature",
      +  "story",
      +  "spec",
      +  "workflow",
      +  "task",
      +  "decision",
      +  "constraint",
      +  "pattern",
      +  "glossary",
      +  "iteration",
      +  "milestone"
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description is free to add what they cannot: the return contract (ranked hits of id, title, type, score, snippet), the fact that only hits and not full content are returned, and that an empty list means no match. It does not mention filter interaction behavior or ranking caveats, but the important behavioral facts are present.

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?

Four short sentences, front-loaded with purpose then capability routing then return shape. "Returns ranked hits ... only" is the key constraint and appears early; no sentence is padding.

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

Completeness5/5

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

With no output schema, the description steps in to define the return fields and empty-result semantics, which is exactly the gap an agent would otherwise hit. For a six-parameter, read-only search tool this is complete enough to invoke correctly on the first try.

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 100%, including enum values and defaults for mode, type, tags, limit, and product, so the schema does the parameter work. The description mentions only "free-text query," adding no meaning beyond the schema's own example strings. Baseline 3 applies.

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

Purpose5/5

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

States a specific verb+resource ("Search the product knowledge vault by free-text query") and explicitly names what it is not: get_concept returns one full note, get_context an assembled briefing. An agent can distinguish it from those siblings without opening any schema.

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

Usage Guidelines4/5

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

"Useful when you need product knowledge but don't yet know which concept ids exist" gives a concrete triggering condition, and the sibling routing sentence clarifies the search-then-fetch flow. It lacks an explicit when-not (e.g., enumerating everything of a type, which list_concepts would cover), so it falls just short of a 5.

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