Appian MCP Server

get_records

Retrieve records from an Appian application by specifying the record type name. Optionally set the maximum number of records to return.

Instructions

Retrieve records from an Appian application using record type name

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "recordName": "<recordName>"
    },
    "name": "get_records"
  }
}

Input Schema

Name	Required	Description	Default
`recordName`	Yes	The name of the Appian record type
`pageSize`	No	Maximum number of records to return (default: 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 17, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. However, it only states the basic action without mentioning authentication, rate limits, error handling, or what happens if the record type doesn't exist. The pageSize parameter hints at pagination but behavior is not described.

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 a single sentence that efficiently conveys the tool's purpose. It is appropriately sized and front-loaded with the key action and resource. Minor room for improvement by adding a brief note on return format.

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

Completeness3/5

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

Given the tool's low complexity (2 parameters, no output schema), the description is minimally adequate. It tells what the tool does and the key parameter. However, it lacks details about return values, error handling, and recordName format, which are gaps for contextual completeness.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (recordName, pageSize) are documented in the schema. The description adds no additional meaning beyond the schema, which meets the baseline for high coverage.

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 'Retrieve records' with the resource 'records from an Appian application' and the method 'using record type name'. It distinguishes from sibling tools like create_labelling_request and get_appian_suppliers, which focus on creating or getting specific entities.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives. While the purpose implies retrieval, there is no guidance on when not to use it or mention of specific contexts (e.g., filtering). The usage is implied but not explicit.

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

Deploy Server