Skip to main content
Glama

Search by meaning

search_semantic
Read-only

Find concepts whose when_to_read matches a situation described in plain words.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe situation, or what you are trying to remember, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing that matching happens against the when_to_read field specifically, not full-text content. It says nothing about result count, ranking, or how matches are ordered.

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?

One tightly constructed sentence with the matching field and input style front-loaded, and no wasted words. Nothing is buried or redundant.

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?

For a one-parameter read-only search with no output schema, the definition covers what it searches and how matches are described. It stops short of stating what a result contains or how many come back, which would help an agent plan a follow-up read_concept call.

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% and the single query parameter is already documented in the schema with nearly identical wording, so the description cannot add much. Baseline 3 applies; the phrase "a situation" reinforces the expected natural-language input style but adds no new constraints.

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?

Specific verb ("Find") and resource ("concepts"), plus the matching mechanism ("whose when_to_read matches") and input mode ("a situation described in plain words"). It does not name the sibling search_keyword, so the agent must infer the semantic-vs-keyword distinction from the name/title alone.

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 agent can infer it should call this when it has a free-text situation rather than exact keywords. There is no explicit when-to-use, no when-not-to-use, and no reference to the obvious alternative search_keyword.

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