Skip to main content
Glama
aol-integration

accurate-schema-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ACCURATE_API_SECRETYesAccurate Online API secret key (required)
ACCURATE_BEARER_TOKENYesAccurate Online API bearer token (required)
ACCURATE_ENABLE_DELETENoSet to 'true' to enable delete operations in generic_call. Defaults to 'false'.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

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_resourcesA

List all Accurate Online API resources available (e.g. 'item', 'vendor', 'purchase-invoice', 'sales-order'). Call this first if you don't know the resource name for what the user is asking about.

schema_lookupA

Look up the fields, parameters, and requirements for a specific Accurate endpoint before calling it. endpoint format is '/', e.g. 'purchase-invoice/save', 'item/list', 'vendor/detail', 'purchase-invoice/delete'. Use list_resources first if you don't know the resource name, or pass just the resource name (e.g. 'item') to see all its endpoints.

generic_callA

Call any Accurate Online endpoint. Always run schema_lookup on the endpoint first so you know the correct field names, required fields, and types. For GET (list/detail) endpoints pass query params in params. For POST (save) endpoints pass the payload in body. For DELETE pass params (usually {'id': ...} or {'number': ...}).

refresh_hostA

Re-resolve which Accurate host this API Token's database lives on. Only needed if requests suddenly start failing in a way that suggests the database migrated to a different host mid-session.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct phase: list_resources for discovery, schema_lookup for metadata, generic_call for execution, and refresh_host for a specific maintenance edge case. There is no meaningful overlap; an agent can easily pick the right tool based on intent.

Naming Consistency4/5

All names use consistent snake_case, which is a strong pattern. However, schema_lookup and generic_call are noun/adj+noun rather than the verb_noun pattern seen in list_resources and refresh_host, a minor deviation from an otherwise predictable convention.

Tool Count5/5

Four tools is well-scoped for a generic API gateway: discovery, schema, execution, and host refresh. Each tool earns its place, and no unnecessary tools bloat the surface.

Completeness4/5

The surface covers discovery, metadata lookup, and execution for any endpoint, enabling full CRUD via generic_call. Minor gaps exist, such as no explicit pagination or batch helper, but these can be handled through generic_call parameters.

Maintenance

ActivitySlowing
ResponsivenessNo issues