Skip to main content
Glama

Innovative Workspace

Search IW case studies

search_case_studies
Read-onlyIdempotent

Search Innovative Workspace's published work (case studies of the products it built, and the client named on the site). Leave the query out to list them. Snapshot of https://www.innovativework.space/ taken on 2026-11-20.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords to look for, in plain language. Leave it out to list everything.

Output Schema

NameRequiredDescriptionDefault
noteNo
workNo
totalYes
resultsYes
snapshotYesThe public site this answer comes from, and when this server took its snapshot of it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: results come from a snapshot of a specific URL taken on 2026-11-20, which tells the agent data may be stale and is bounded. It stops short of describing result ordering or matching semantics (substring vs. keyword).

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 corpus definition comes first, the enumeration behavior second, and the provenance/snapshot caveat last — an effective front-to-back ordering for an agent scanning the definition.

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 rich annotations, a fully documented single parameter, and an output schema handling return values, the description only needs to establish scope and provenance — which it does, including the snapshot date. The remaining gap is search semantics, which an agent might want when constructing a query, but it is minor given the schema coverage.

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% for the single optional 'query' parameter, and the description's 'Leave the query out to list them' largely restates the schema's own 'Leave it out to list everything.' It adds no matching-behavior detail (e.g., how words are combined) beyond what the schema provides, so the 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?

States a specific verb and resource ('Search Innovative Workspace's published work') and clarifies the corpus with a parenthetical listing case studies and the named client. This distinguishes it from sibling searches like search_services or search_experts by naming the content domain, though it never names get_case_study as the single-item alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is 'Leave the query out to list them,' which describes how to enumerate rather than when to pick this tool over get_case_study or the other search_* siblings. Usage is implied by the verb and content domain, but no exclusions or alternatives are stated.

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