Skip to main content
Glama
yourlastnamesoundslikeatypeofpasta

Acumatica MCP Server

describe_entity

Retrieve full metadata for any Acumatica entity, including valid fields, key format, actions, and sub-collections, to correctly construct API calls.

Instructions

Return the full metadata for an entity: fields, key format, actions, and sub-collections.

Always call this before list_records or get_record when you are unsure of:

  • which field names are valid (use these in select= and filter= expressions)

  • how to format the id= argument for get_record / delete_record

  • which sub-collections can be passed to expand=

Args: entity: Entity name, e.g. "SalesOrder", "Bill", "Customer".

Returns one of two shapes:

Normal entity (has a key): { "entity": "SalesOrder", "fields": ["OrderType", "OrderNbr", "CustomerID", ...], # valid $select / $filter names "key_fields": ["OrderType", "OrderNbr"], # fields that make up the URL key "key_format": "Slash-separated: /", # how to build the id= string "actions": ["CancelSalesOrder", ...], "expand": ["Details", "Shipments", ...] }

Query-only entity (inquiry/summary view - no addressable key): { "entity": "AccountSummaryInquiry", "query_only": true, "note": "This entity has no addressable key - use list_records with filter= only. ...", "fields": [...], "actions": [], "expand": [] } For query-only entities: do NOT call get_record - pass at least one filter= to list_records. Calling list_records with no filter on these entities returns HTTP 500 on this tenant.

Returns {error: "Unknown entity"} if the entity is not in the catalog.

Examples: describe_entity("SalesOrder") # -> key_format: "Slash-separated: /" # -> use get_record("SalesOrder", "QT/I004264")

describe_entity("Bill")
# -> key_format: "Slash-separated: <Type>/<ReferenceNbr>"
# -> use get_record("Bill", "Bill/012979")

describe_entity("AccountSummaryInquiry")
# -> query_only: true
# -> use list_records("AccountSummaryInquiry", filter="Period eq '202506'")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but the description fully discloses behavior: two return shapes for normal vs query-only entities, error response for unknown entities, and concrete examples. It also notes that query-only entities have no addressable key.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately long but well-structured: a one-line summary, usage instructions, Args section, and two return shapes with examples. It is front-loaded with the main purpose. Some redundancy could be trimmed, but overall clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (different handling for normal vs query-only entities) and the presence of an output schema, the description provides complete contextual information: when to use, what to expect, and edge cases. No gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'entity' has 0% schema coverage, but the description adds value by specifying it as the entity name with examples (e.g., 'SalesOrder'). While sufficient for a simple parameter, the examples are helpful but not exhaustive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns full metadata for an entity including fields, key format, actions, and sub-collections. It distinguishes itself from siblings like list_entities by specifying the exact information provided.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises calling this tool before list_records or get_record when uncertain about field names, id format, or expand parameters. It also differentiates between normal and query-only entities, warns against calling get_record on query-only entities, and mentions HTTP 500 risks without filters.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yourlastnamesoundslikeatypeofpasta/acumatica-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server