Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_wildcard_prompts

List wildcard prompt snippets that apply to every flow step, enabling cross-cutting instructions without manual repetition.

Instructions

List the tenant's wildcard prompt snippets — those that apply to EVERY flow step (they sit at the top of each step's prompt stack). Use this for cross-cutting instructions that should hold everywhere, rather than attaching the same snippet to every step by hand. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_wildcard_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

The description declares the tool as read-only and explains the behavioral trait that wildcard snippets sit at the top of each step's prompt stack. With no annotations provided, the description adequately covers the safety and behavior of the tool, though it could mention pagination or limits.

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 consists of two sentences that front-load the core action and then provide context. Every word is purposeful, with no redundancy or unnecessary details.

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?

For a simple list tool with no parameters and no output schema, the description is largely complete. It explains what is listed, the concept of wildcards, and the read-only nature. It could mention the return format or pagination, but the information given is sufficient for an agent to understand and invoke the tool correctly.

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 input schema has no parameters (100% coverage), so baseline is 3. However, the description adds significant meaning beyond the schema by explaining what the listed items are (wildcard prompt snippets) and their purpose, which the empty schema does not convey.

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's purpose: listing wildcard prompt snippets that apply to every flow step. It uses specific verb 'List' and resource 'wildcard prompt snippets', and distinguishes from other sibling tools like list_prompt_snippets by explaining what makes them special.

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 explicitly advises using this tool for cross-cutting instructions that should hold everywhere, contrasting with manually attaching snippets per step. While it doesn't name an alternative tool like list_prompt_snippets, the guidance is clear and useful for deciding when to use it.

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