Skip to main content
Glama

List case studies

list_work
Read-onlyIdempotent

Published case studies in the agency's own order, 1 to 20 per page, each with client, year and summary. The optional query filters by title, client or summary (e.g. "Mashreq"). Use get_work with a slug for one case study's services and summary.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many case studies to return, from 1 to 20.
queryNoWords to match against the title, client or summary.
cursorNonext_cursor from the previous page; takes precedence over offset.
offsetNoHow many matching case studies to skip, for paging (0 for the first page).

Output Schema

NameRequiredDescriptionDefault
itemsYes
limitYes
totalYes
offsetYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds meaningful behavior beyond that: results come back in the agency's own order, page size is capped at 20, and each item carries client/year/summary. No permission or rate-limit notes are offered, but none are needed for a public read listing.

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, front-loaded with what is returned, then the filter and the alternative tool. No filler, and the ordering/page-size constraint appears before the sibling reference where it matters most.

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?

An output schema exists and the per-item fields are summarized, while cursor/offset paging is fully documented in the schema. Minor gaps remain, such as whether query matching is case-insensitive or how ordering behaves with filtered results, but nothing blocks a correct 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 description coverage is 100%, so limit, query, cursor and offset are all already documented in the schema. The description reinforces the page-size range and adds a concrete query example ("Mashreq"), but adds no syntax or precedence detail beyond the structured fields — baseline 3.

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+resource (published case studies), the ordering, the page-size range, and the per-item fields returned (client, year, summary). It also contrasts itself with get_work for a single case study, so an agent can distinguish it from the sibling without opening either 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 routing: use the query filter to match title/client/summary, and use get_work with a slug when a single case study's detail is needed. It stops short of stating when-not to use the filter (e.g. that browsing in agency order is the default), but the usage context is unambiguous.

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