portal-api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORTAL_ENV | Yes | Environment: sandbox or production | |
| PORTAL_APP_ID | Yes | API application key | |
| PORTAL_BASE_URL | Yes | Base URL for Portal API | |
| PORTAL_SECRET_KEY | Yes | Secret key for HMAC signing | |
| PORTAL_USER_API_KEY | Yes | Base64-encoded User API Key from credential exchange, typically 44 characters | |
| PORTAL_WRITE_ENABLED | No | Enable write operations (not yet supported) | false |
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 |
|---|---|
| test_connectionA | Confirm that the configured Portal.io API credentials work. This is read-only and returns only proposal metadata. |
| list_proposalsB | List or search Portal.io proposals. Read-only. |
| get_proposalA | Get complete details for one Portal.io proposal. Read-only. |
| list_usersA | List active users in the Portal.io account. Use this to find salesperson IDs. Read-only. |
| search_contactsB | Search or list Portal.io contacts. Read-only. |
| search_catalogB | Search the Portal.io catalog. Catalog API access must be enabled for the account. Read-only. |
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
Each tool targets a distinct resource and action: proposals (get/list), users (list), catalog (search), contacts (search), and connection test. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_proposal, list_users, search_catalog).
6 tools is appropriate for a read-only API surface covering proposals, users, catalog, contacts, and connection verification.
Covers the main read operations for key entities, but lacks get_user or get_contact individually; however, this is reasonable for the scope.