Skip to main content
Glama

Developh case studies

list_case_studies
Read-only

Published client work by Developh with links to each case study. Filter by sector (the ones with published cases so far; a missing sector means no case is published yet, not that the studio does not take it on) or service (websites, online stores, branding, web apps) to get what was built in each case; with no filter, lists every published project.

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
localeNoAnswer language: English (en) or European Portuguese (pt).en
sectorNoSector: restaurants, tourism, clinics, automotive, real-estate, software, events, industry, education.
serviceNoService: websites, online-stores, branding, web-apps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / sector / description
      Previous value: -"Sector: restaurants, tourism, clinics."New value: +"Sector: restaurants, tourism, clinics, automotive, real-estate, software, events, industry, education."
    • changedInput schema / properties / sector / enum
      Previous value: -[
      -  "restaurants",
      -  "tourism",
      -  "clinics"
      -]New value: +[
      +  "restaurants",
      +  "tourism",
      +  "clinics",
      +  "automotive",
      +  "real-estate",
      +  "software",
      +  "events",
      +  "industry",
      +  "education"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful context beyond them: results include links, filtering narrows rather than excludes, and an absent sector is a publishing state, not a capability gap. Pagination or result-size behavior is unstated, but this appears to be a small static catalog.

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?

It is compact and front-loaded: the deliverable comes first, then filter semantics, then the default case. The parentheticals are dense but each carries a real caveat, so nothing is filler, though the single run-on sentence is harder to parse than a short bulleted structure would be.

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?

Three optional parameters, no output schema, and annotations covering safety mean the description's remaining job is to explain what is returned and how filters compose, which it does (case studies plus per-case links; filters narrow; no filter returns all). Only the locale parameter's role in answer language is left unaddressed.

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 enums and their meanings are already documented; the baseline would be 3. The description earns above baseline by explaining the semantics of the sector enum's sparsity and by restating the service options and the no-filter default (return all published projects), adding behavioral meaning rather than repeating syntax. It says nothing about the locale parameter's effect, a small omission.

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?

The description identifies the resource precisely ("Published client work by Developh with links to each case study") and states that results include links to each case study. It clearly reads as a listing tool, distinguishing it in kind from request_contact and run_website_audit, though it never names a sibling or explicitly contrasts with studio_info.

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?

Usage is well-specified: filter by sector or service to get what was built in each case; with no filter, every published project is returned. The clarification that a missing sector means no case is published yet (not that the studio declines that sector) heads off a realistic misuse. It stops short of explicit when-not-to-use guidance relative to the other studio tools.

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