ResultGate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assess_browseract_fitC | Choose free/existing API/reject/consider Basic based on need, never commission; prepare bounded task and official handoff. No authorization to spend. |
| validate_browseract_reportA | Check completeness of up to 20 product results and supplied samples. No fetching or truth certification; errors stay explicit. |
| validate_browseract_csvC | Validate a max-20-row BrowserAct CSV against expected URLs. Preserve original strings; no currency inference, provider calls, payment or telemetry. |
| list_referral_providersC | List six researched provider cards and unresolved eligibility, prices and payout terms. Not contracted sellers; no execution. Affiliate status and disclosure are explicit. |
| recommend_referral_serviceB | Match an explicit need to capability; reject unsafe scope, prefer existing/local/free. Budget is not authorization. No commission-based ranking. |
| prepare_referral_taskB | Return provider-specific task, example, output fields and official connection steps. No execution, account creation, secrets, purchase or attribution. |
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 6 tools
The set splits cleanly into a BrowserAct cluster and a referral cluster, with verbs that signal intent (assess vs validate vs list vs recommend vs prepare). The only real overlap is between validate_browseract_report and validate_browseract_csv, which both check output correctness but differ by input format (sample results vs CSV rows).
Every tool follows the same verb_noun snake_case pattern (assess_, validate_, list_, recommend_, prepare_) with the domain object appended. Subdomains are encoded predictably as browseract_* and referral_*.
Six tools is well-scoped for a narrow advisory/gate server: three cover the browser-automation path and three cover the referral path. No tool looks like filler or a near-duplicate.
The lifecycle is covered for both paths: assess fit, validate outputs, enumerate providers, match need, and prepare the handoff task. Minor gaps exist (e.g., validation only covers report/CSV formats at a capped size, no explicit tool to restate spend/authorization constraints standalone), but agents can work around these within the described scope.