Skip to main content
Glama

server

get_case_studies

Read-onlyIdempotent

Use when you need verified Yari Infotech engineering case studies, architecture decisions, and measured business outcomes. Returns public project slugs, industries, summaries, metrics, and canonical URLs.

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": "get_case_studies"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryNoOptional industry keyword filter such as 'hospitality', 'commerce', 'logistics', or 'growing-businesses'. Omit to list all public case studies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the important scoping detail that only *public* case studies are exposed, but says nothing about result volume, ordering, or rate limits. A modest but real addition over the structured fields.

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, no filler. The usage trigger is front-loaded and the second sentence enumerates return content compactly, which matters because there is no output schema.

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 simple one-parameter read tool with no output schema, the description covers both when to call it and what comes back. The only real gap is silence on the industry filter and result-set size, which the schema largely handles for the former.

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% and the single optional industry parameter, including its 'omit to list all' behavior, is fully documented in the schema. The tool description never mentions the filter at all, so it adds no meaning beyond the schema; baseline 3 applies.

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 names the specific resource (Yari Infotech engineering case studies, architecture decisions, business outcomes) and what it yields (project slugs, industries, summaries, metrics, canonical URLs). It is clearly distinguishable from get_services and estimate_project by resource, though it never explicitly contrasts itself with them.

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?

The opening clause 'Use when you need verified...' gives an explicit trigger condition tied to the content type sought. It stops short of naming alternatives or stating when NOT to use this tool, so the agent must infer that estimate_project is the right call for pricing questions.

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