Skip to main content
Glama

Ergini: hire an AI engineer

Find matching use cases

find_use_cases
Read-onlyIdempotent

Search Ergin's library of worked AI use cases (support agents, invoice and document automation, sales and lead handling, internal knowledge assistants, MCP servers, legacy rescue and more) for the ones closest to a problem. Pass the problem in plain words, ideally with the systems involved (for example 'supplier invoices arrive by email and get typed into Xero'). Returns the best matches with a one-line summary, the page URL and the typical price range. Follow up with get_use_case for details.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matches to return, 1 to 10. Defaults to 5.
queryYesThe problem or task in plain words, with the systems involved if known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds value beyond them by disclosing the return shape (one-line summary, page URL, typical price range) and the follow-up path for deeper detail. It does not mention match-count limits or ranking behavior, which keeps it from 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?

Front-loads the core action and keeps the category list inline in parentheses rather than exploding it into bullets. The parenthetical enumeration is slightly long, but every clause (searchable scope, example query, return shape, follow-up) carries information an agent needs.

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?

No output schema exists, and the description compensates by stating exactly what comes back (best matches with summary, URL, price range). With annotations covering the safety profile and the schema fully documenting both parameters, nothing material is missing for correct invocation.

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% with good inline descriptions for both query and limit, so the baseline is 3. The description nudges above baseline by giving a concrete example query ('supplier invoices arrive by email and get typed into Xero') that demonstrates the intended granularity, though the limit parameter is not discussed at all.

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?

Names a specific verb (search) and a concrete resource (Ergin's library of worked AI use cases), enumerates the domain categories it covers, and explicitly separates itself from get_use_case, which returns details. An agent can distinguish it from siblings like list_case_studies or list_services without opening any other 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?

Gives clear usage conditions: pass the problem in plain words, ideally naming the systems involved, with a worked example of the expected phrasing. It also routes the agent forward ('Follow up with get_use_case for details'). There is no explicit statement of when not to use it or what to do if the search returns nothing, but the positive guidance is strong.

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