Skip to main content
Glama

AdCritter for Builders

by com.adcritter

adcritter_get_platform_overview

Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries full burden. It goes beyond a simple overview by warning that tool descriptions/parameter names are conceptual and do not match actual API routes, field names, or response shapes. This is a significant behavioral caveat for the entire toolset.

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 compact and front-loaded with 'Start here.' Every sentence earns its place: overview contents, API client distinction, and pointer to the reference tool. 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?

For a zero-parameter, no-output-schema tool, the description fully explains what it returns, how it fits into the workflow, and what to do next. It is complete and even adds cross-tool context.

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?

The tool has 0 parameters, so a baseline of 4 applies. The description adds context about the tool's role but needs no parameter clarification since none exist.

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 'Returns the AdCritter platform overview' and lists specific contents (entity hierarchy, happy path, navigation). The opening 'Start here' distinguishes it as the entry point among siblings.

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

Usage Guidelines5/5

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

'Start here' explicitly indicates when to use this tool. It also names adcritter_get_api_reference as the necessary next step before coding, providing clear alternatives and exclusions.

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

All AdCritter for Builders toolsInspect
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.1/5.0
Disambiguation2/5

Multiple tools serve as entry points (adcritter_build_app and adcritter_get_platform_overview both say 'Start here') and several guidance tools (guidance, get_usage_guide, get_design_guide, get_api_reference) have overlapping descriptions around API endpoints and workflows. Agents would need to parse subtle differences to choose correctly, making misselection likely.

Naming Consistency4/5

Five of seven tools follow a verb_noun pattern (adcritter_get_*), but adcritter_guidance and adcritter_health are bare nouns, breaking the pattern. The prefix is consistent and all snake_case, so the deviations are minor.

Tool Count5/5

Seven tools is within the ideal 3-15 range and fits the server's purpose as a guidance/reference library. Each tool addresses a distinct aspect of the builder journey, though some overlap in content.

Completeness4/5

The server covers platform overview, API contracts, design guidance, usage workflows, feature-specific build instructions, and health checks. It lacks a direct tool for listing all available entities or guides (buried in other tools), but the core backing need is well covered. The overlap doesn't create dead ends, just confusion.

Resources