Skip to main content
Glama

Ergini: hire an AI engineer

List case studies

list_case_studies
Read-onlyIdempotent

List the products Ergin has shipped and written up as case studies at ergini.com/work, each with the customer's problem in one line, the fix in one line and the page URL. Use it when the user asks for proof, past work or examples.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_case_studies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description need not restate safety. It adds genuinely new context by describing the shape of each returned entry (problem in one line, fix in one line, page URL), which is valuable precisely because there is no output schema.

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?

Two sentences, both earning their place: the first defines the resource, its location and the per-item payload; the second routes the agent to the right request type. The scope statement is front-loaded and nothing is repeated from the title or annotations.

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?

With no parameters and no output schema, the description carries the burden of explaining the return value, and it does so competently by describing the three per-item fields. It stops short of saying whether the list is exhaustive or how many entries to expect, which leaves a small gap for an agent reasoning about result size.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly says nothing about arguments rather than padding with filler.

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?

States a specific verb and resource ("List the products Ergin has shipped and written up as case studies at ergini.com/work") and even enumerates the per-item fields the agent will get back, so the operation is unmistakable. It does not differentiate itself from the sibling tools find_use_cases or get_use_case, which is the only thing keeping it from a 5.

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?

"Use it when the user asks for proof, past work or examples" gives a concrete, recognizable trigger condition rather than a vague restatement. There are no explicit when-not conditions and no named alternative for the case where the agent wants a single case study rather than the full list.

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