Skip to main content
Glama

Get one case study

get_work
Read-onlyIdempotent

One published case study by its slug (from list_work or search_site): client, year, services, summary, short TL;DR and page URL.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe case study slug, e.g. from list_work.

Output Schema

NameRequiredDescriptionDefault
urlYes
slugYes
tldrYes
yearYes
titleYes
clientYes
summaryYes
servicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds one useful behavioral fact — only *published* case studies are returned — but the rest of the sentence re-lists return fields that the output schema already documents, adding little beyond structured data.

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?

A single sentence with zero filler, front-loading the resource and the required input before enumerating what is returned. Nothing is repeated or padded, and the parenthetical about slug provenance is placed exactly where the reader needs it.

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?

For a one-parameter, read-only lookup with an output schema, this covers everything an agent needs to invoke it correctly: the input, where to get it, the published-only constraint, and the payload contents. The only shortfall is the absence of failure behavior for an unknown or unpublished slug.

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% and the slug parameter already has its own description with an example, so the baseline would be 3. The definition earns an extra point by stating where slugs come from (list_work or search_site), which is provenance information the schema does not carry and which directly helps an agent obtain a valid value.

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 definition names a specific resource and scope: one published case study retrieved by slug, and it lists what comes back (client, year, services, summary, TL;DR, page URL). It is clearly distinct from list_work and search_site, which are referenced as the slug sources rather than as alternatives for the same job.

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?

It gives the key precondition for use — you must already have a slug, obtained from list_work or search_site — which implicitly routes an agent away from calling it with arbitrary text. There is no explicit when-not guidance (e.g. what to do if the slug is unknown or the study is unpublished), so it stops short of a 5.

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