growthmak

Find case studies

find_case_studies

Find Growthmak client case studies filtered by industry, market or service. Returns the challenge, the approach and the measured results. Use this to answer 'have you worked with businesses like mine?'. Filters are matched loosely, so 'manufacturing' matches 'Manufacturing · Construction' and 'USA' matches 'Houston, TX, USA'. Omit a filter rather than guessing at its value.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`market`	No	e.g. 'USA', 'Dubai', 'Australia', 'India'
`service`	No	e.g. 'Google Ads', 'SEO', 'web development', 'CRO'
`industry`	No	e.g. 'ecommerce', 'manufacturing', 'franchise', 'SaaS'

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses loose matching behavior with examples ('manufacturing' matches 'Manufacturing · Construction'), explains the return content, and advises against guessing filters. It could mention sorting or pagination, but the provided details are clear and sufficient.

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?

The description is three sentences, each essential. The first sentence states the verb and resource, the second clarifies the use case, and the third explains matching behavior. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (zero required params, no output schema), the description fully covers what an agent needs: what it does, what it returns, how filtering works, and when to use it. It is complete for its complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning beyond the input schema: it explains the loose matching logic, provides concrete examples for market and industry, and explicitly advises to omit rather than guess parameters. Schema coverage is 75%, and the description compensates fully for the remaining gaps.

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?

The description clearly states the tool finds Growthmak client case studies filtered by industry, market, or service, and specifies the return fields (challenge, approach, results). It distinguishes from sibling tools by focusing specifically on case studies rather than audits, coverage checks, or packages.

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 description explicitly states the use case: 'Use this to answer "have you worked with businesses like mine?"' and advises omitting filters rather than guessing. However, it does not mention when not to use this tool or directly compare to siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All growthmak tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: book_growth_audit returns a booking link, check_market_coverage checks geographic coverage, find_case_studies retrieves case studies, get_growth_engine explains the Growth Engine system, get_packages lists packages, get_page retrieves a specific page, and search_growthmak is a fallback search. There is no overlap or ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun pattern (e.g., book_growth_audit, check_market_coverage, find_case_studies, search_growthmak), but get_growth_engine and get_page deviate slightly with 'growth_engine' and 'page' not being as uniformly structured. The naming is consistent and readable overall.

Tool Count5/5

With 7 tools, the set is well-scoped for a marketing consultancy's MCP server. Each tool covers a distinct functional area (booking, geographic coverage, case studies, system explanation, packages, page retrieval, and search). No tool feels redundant or missing.

Completeness4/5

The server provides good coverage for key interactions: it can inform about services, packages, case studies, and booking. A minor gap is the lack of a tool to submit contact details or make a booking directly, but this is explicitly documented as out of scope. The surface feels complete for its stated purpose of information provision.

Resources

Need Help?