Skip to main content
Glama

magne.tools

Search tools

search_tools
Read-only

Keyword search over the published catalog, with the site's full-text filters (Turkish task phrases, country words such as "turkey", facets such as "free" or "open source"); every word is read as finished, never as a prefix: up to 12 tools in rank order, each once, with id, name, kind, tagline, pricing and tool page URL, and the catalog tasks a Turkish phrase in the query named (often none for English queries; use list_tasks for those). One job per call: search 'send email' and 'accept payments' separately. Results are not judged for fit, so check them with get_tool.

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

Input Schema

NameRequiredDescriptionDefault
queryYesA few words naming the job, e.g. "send transactional email" or "accept payments in turkey".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds real behavioral facts: a hard 12-result cap, rank ordering, de-duplication ("each once"), the exact fields returned, and that results are unranked for fit and must be validated with get_tool. The tokenization rule ("every word is read as finished, never as a prefix") is a notable non-obvious behavior. It stops short of describing pagination or empty-result behavior, so not a 5.

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?

Purpose and scope are front-loaded, and the trailing routing sentences each carry distinct information. The opening sentence is very long with stacked parentheticals, making it denser than necessary to scan, though no sentence is pure filler.

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 compensates by enumerating the returned fields and result count, and it closes the loop on the downstream workflow (verify with get_tool). Nothing an agent needs to call this correctly — input format, result shape, limits, follow-up — is missing.

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% and already gives an example query, so the baseline would be 3; the description earns more by explaining how query text is interpreted (full-text filters, Turkish task phrases, country words, facets) and the exact-match, non-prefix token rule that the schema does not convey.

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 and resource ("keyword search over the published catalog") and immediately bounds scope: up to 12 tools, rank order, each once, with named result fields. It also differentiates itself from siblings by naming list_tasks for English-query task lookup and get_tool for fit checking.

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

Usage Guidelines5/5

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

Gives explicit routing: use list_tasks when the query should surface catalog tasks, and use get_tool to verify results. It also states a usage constraint — "one job per call: search 'send email' and 'accept payments' separately" — which is a concrete when/when-not rule rather than implied guidance.

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