Reach Dog MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REACHDOG_API_KEY | Yes | Your Reach Dog account's API key created in the developer console. | |
| REACHDOG_API_URL | No | The Reach Dog API URL. | https://api.reach.dog |
| REACHDOG_ACCOUNT_LABEL | No | An account label identifying your application. | |
| REACHDOG_MAX_TOKENS_PER_SESSION | No | A whole number limiting estimated spending across the process, counted in Reach Dog billing tokens. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_usageB | Read account usage and current unit price. |
| list_parametersC | List available API parameters, grouped by endpoint. |
| estimate_costC | Estimate one title, research or content request in Reach Dog tokens. |
| enrich_titleC | Preview by default. Set confirm to request approval for this exact body. |
| research_marketC | Preview by default. Set confirm to request approval for this exact body. |
| generate_contentC | Preview by default. Set confirm to request approval for this exact body. |
| enrich_catalogC | Submit a catalog for a quote with body. Accept a previously displayed quote with batch_id, acceptance and confirm=true. |
| get_catalog_statusC | Read current catalog status and settled results. |
| retry_paymentB | Request approval to retry a refused payment for the original accepted quote. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have clearly distinct purposes: cost estimation, usage lookup, parameter discovery, content operations, catalog operations, and payment retry. The three content-generation tools share very similar generic descriptions, but their names still distinguish title enrichment, market research, and content generation.
All tool names use a consistent snake_case verb_noun pattern, such as estimate_cost, get_usage, enrich_title, and retry_payment. The few longer names like get_catalog_status remain predictable and readable.
Nine tools is well scoped for this API surface, covering estimation, account state, schema discovery, content workflows, catalog workflows, and payment retry. Each tool appears to earn its place without obvious filler.
The set covers the main lifecycle: estimate cost, inspect usage and parameters, run title/research/content operations, submit and track catalog enrichment, and retry payment. Minor gaps may exist around retrieving status or results for non-catalog content requests, but core workflows are represented.