outmate-gtm-router
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JINA_API_KEY | Yes | Your Jina API key, used by the jina_read_url tool. Declared as a sensitive userConfig value in the Claude Code plugin manifest (or set in a local .env for development). | |
| TAVILY_API_KEY | Yes | Your Tavily API key, used by the tavily_search tool. Declared as a sensitive userConfig value in the Claude Code plugin manifest (or set in a local .env for development). |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tavily_searchA | Search the live web for company, product, market, competitor, prospect, technology, pricing, or news research. Use this tool to DISCOVER relevant webpages and source URLs. It returns ranked titles, URLs, snippets/content, and an optional short answer. Use jina_read_url when a specific result needs deeper page extraction. Do not use this tool to read a URL already known to the user. |
| jina_read_urlA | Extract the readable content of one specific public webpage as LLM-friendly Markdown/text. Use this tool when the user supplies a URL or after tavily_search has found a relevant source that needs detailed inspection. This is a page-reading tool, not a search engine. It only accepts public HTTP/HTTPS URLs; never use it for localhost, private networks, or authenticated/private pages. |
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 2 tools
The two tools have clearly separate roles: tavily_search discovers web sources, while jina_read_url extracts content from a known URL. The descriptions explicitly cross-reference each other and warn against using one in place of the other, leaving no meaningful ambiguity.
Both names use lowercase snake_case with a vendor prefix and an action-oriented second component. The pattern is mostly predictable, though jina_read_url includes an object ('url') while tavily_search does not, a minor inconsistency.
Two tools is thin for a server named as a GTM router, even though the search-and-read pair is coherent. It is functional but borderline under-scoped for broader go-to-market research workflows.
The pair covers the core web-research lifecycle: discover relevant sources and then read a specific page. Minor gaps remain, such as batch reading or structured extraction, but no critical dead end is apparent for the stated purpose.