Skip to main content
Glama
Sign In
Appian MCP Server

Appian MCP Server

by cmsappian123-bit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_appian_suppliers

Fetch active available suppliers filtered by business category from the Appian Data Fabric.

Instructions

Fetches a list of active available suppliers from the Appian Data Fabric based on a given domain/category.

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": {
      "category": "<category>"
    },
    "name": "get_appian_suppliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesThe business category filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool performs a read operation (fetch), but lacks details on pagination, authentication, rate limits, or return format. The description is minimally adequate for a simple read tool.

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

Conciseness5/5

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

The description is a single sentence of 16 words, front-loaded with the verb and object. Every word is necessary and no extraneous information is present.

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

Completeness4/5

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

Given the simple nature (one required parameter, no output schema), the description covers the core purpose and parameter. It lacks behavioral details and return structure, but remains fairly complete for a straightforward fetch tool.

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% with the parameter 'category' described as 'The business category filter.' The description adds 'based on a given domain/category' which is redundant. It does not significantly enhance understanding beyond the schema.

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 verb 'fetches', the resource 'suppliers', the source 'Appian Data Fabric', and the condition 'active available'. It also specifies filtering by domain/category, distinguishing it from sibling tools like create_labelling_request or get_records.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: when needing a list of active available suppliers filtered by category. However, it does not explicitly mention when not to use it or suggest alternative tools, though the context is sufficient for the agent.

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

Deploy Server

Other Tools