RaportAgent MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_report | Start a RaportAgent market/compliance research report. Typically takes ~15 min, occasionally longer under load (hard timeout: 45 min), so this returns a report_id immediately (status: queued) unless you set wait_seconds. Use get_report_status to poll, then get_report to fetch the finished markdown. Costs 1 credit (2 credits for the 'battlecard' template). |
| get_report_statusA | Check whether a report is queued, in_progress, completed, failed, or cancelled. |
| get_reportA | Fetch a completed report's full markdown content and section list. |
| get_report_auditA | Get a report's audit trail / provenance: AI models, agents, source counts, and a SHA-256 of the exact content. Useful for compliance review and verifying a report has not been altered. |
| get_report_sources | List every source cited in a report with link-health counts (working / uncertain / dead) and how many are actually cited inline. Use this to decide whether a report is trustworthy enough to act on, or whether to regenerate it. |
| cancel_report | Cancel a report that is still queued or in progress and refund its credit. Fails if the report has already completed or failed (nothing to cancel at that point). |
| list_reports | List your recent reports (most recent first). |
| get_accountA | Show your RaportAgent account: remaining credits and plan. |
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 4 tools
Each tool targets a distinct aspect: status, content, audit trail, and account info. There is no functional overlap.
All tools follow a consistent 'get_<noun>' pattern, making it predictable for an agent.
With four tools, the set is well-scoped for a reporting and account service—neither overly sparse nor bloated.
The tools are entirely read-only; missing essential CRUD operations like creating, cancelling, or listing reports, which are critical for end-to-end report management.