intacct-docs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPEC_DIR | No | Directory scanned for *.openapi.yaml files | ../data/sage-intacct-rest-api |
| HTTP_HOST | No | Bind address for HTTP transport (0.0.0.0 for all interfaces) | 127.0.0.1 |
| HTTP_PORT | No | Port when using HTTP transport | 3000 |
| LOG_LEVEL | No | error, warn, info, or debug | info |
| TRANSPORT | No | stdio or http | stdio |
| MAX_BODY_BYTES | No | Maximum HTTP request body size in bytes | 1048576 |
| RATE_LIMIT_RPM | No | Max requests per minute per IP (HTTP transport) | 60 |
| MAX_RESPONSE_CHARS | No | Response size cap — output is truncated with a notice when exceeded | 12000 |
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 |
|---|---|
| get-endpoint-docsA | Get complete documentation for a specific API endpoint including parameters, request/response schemas, and examples. Example: method=GET, path=/objects/general-ledger/account/{key} |
| search-endpointsA | Search for API endpoints by path, operation ID, summary, or description keywords. Supports fuzzy matching and multi-word queries. Example: query="create invoice" limit=5 |
| get-schemaA | Get detailed schema definition including all properties, types, and constraints. Example: schemaName=general-ledger-account |
| list-tagsA | List all API tags/categories with endpoint counts. |
| list-schemasB | List all available schema names, optionally filtered by prefix. Example: prefix="general-ledger" |
| get-endpoints-by-tagA | Get all API endpoints for a specific tag/category. Use list-tags first to see available tags. Example: tag="Accounts Payable" |
| generate-exampleA | Generate an example JSON request body for an API endpoint. Example: method="POST", path="/objects/accounts-payable/vendor" |
| spec-quality-reportC | Analyze OpenAPI spec documentation quality. Returns a score and list of issues. |
| healthA | Report readiness status and index statistics. Useful for readiness probes. |
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
Each tool has a distinct focus: endpoint docs, endpoint search, schema retrieval, tag/schema listings, example generation, health, and spec quality. There is minor overlap between search-endpoints and get-endpoints-by-tag, and between get-endpoint-docs and generate-example, but descriptions make the differences clear.
Most tool names consistently follow a verb_noun pattern with lowercase hyphenation, such as get-endpoint-docs, list-tags, and search-endpoints. A few exceptions like health and spec-quality-report break the pattern slightly, but the overall style is predictable and readable.
Nine tools is an appropriate size for a documentation server. The toolset covers discovery, retrieval, schema access, example generation, and operational health without feeling bloated or sparse.
The toolset provides a complete workflow for API documentation consumers: discovering endpoints, retrieving endpoint details, exploring schemas, listing categories, and generating examples. The addition of health and spec-quality-report tools extends the surface sensibly rather than leaving obvious gaps.