Skip to main content
Glama

Ergini: hire an AI engineer

Get one use case

get_use_case
Read-onlyIdempotent

Get one use case from Ergin's library by its slug (from find_use_cases, or the last part of its ergini.com/use-cases URL): the summary, what the AI does and what people still do, every system it touches, the service it is built as, its typical price tier from the published price table, and related use cases. A hub slug (such as 'finance' or 'shopify') returns the hub and its use cases instead.

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": {
      "slug": "<slug>"
    },
    "name": "get_use_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe use case or hub slug, e.g. 'invoice-processing-automation', or its full URL.

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral information: the dual-mode response for hub slugs versus individual use-case slugs, and an enumeration of returned fields (summary, AI vs human tasks, systems, service, price tier, related use cases) despite no output schema existing. It doesn't say what happens on an unknown slug, 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-loaded with the action, then the return payload, then the hub-slug edge case last — a logical order. It is a dense single sentence, but nearly every clause carries information an agent needs; only the parenthetical URL example is arguably expendable.

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?

One required parameter, no output schema, and the description compensates by listing the returned fields and the alternate hub response shape. Nothing an agent needs to invoke this tool correctly — input format, slug source, return contents, edge case — 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%, so the baseline is 3, but the description goes beyond the schema by explaining slug provenance (find_use_cases output or the trailing segment of an ergini.com URL) and by noting that hub slugs such as 'finance' or 'shopify' are also valid values with different semantics.

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 (get one use case by slug) and enumerates exactly what the record contains, which distinguishes it from the sibling find_use_cases that returns plural results. It also explicitly references find_use_cases as the source of slugs, separating lookup from search.

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?

Tells the agent where a valid slug comes from ('from find_use_cases, or the last part of its ergini.com/use-cases URL') and warns that hub slugs take a different code path returning a hub plus its use cases. It stops short of an explicit 'do not call this to search' rule, but the source-of-slug guidance covers the practical selection decision.

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