Skip to main content
Glama
mafzaal

Dynamics 365 Finance & Operations MCP Server

by mafzaal

d365fo_search_actions

Search for available OData actions in D365 Finance & Operations using keyword queries. Filter results by entity, binding type, or function status.

Instructions

Search for available OData actions in D365 F&O using simple keyword-based search.

IMPORTANT: When searching for actions, break down user requests into individual keywords and perform MULTIPLE searches:

  1. Extract keywords from requests (e.g., "posting actions" → "post", "posting")

  2. Perform separate searches for each keyword using simple text matching

  3. Combine and analyze results from all searches

  4. Look for actions that match the combination of concepts

SEARCH STRATEGY EXAMPLES:

  • "posting actions" → Search for "post", then look for posting-related actions

  • "validation functions" → Search for "valid" and "check", then find validation actions

  • "workflow actions" → Search for "workflow" and "approve", then combine results

Use simple keywords, not complex patterns. Actions are operations that can be performed on entities or globally.

Args: pattern: Simple keyword or text to search for in action names. Use plain text keywords, not regex patterns. For requests like 'posting actions': 1) Extract keywords: 'post', 'posting' 2) Search for each keyword: 'post' 3) Perform multiple searches for related terms 4) Analyze combined results. Use simple text matching. entityName: Optional. Filter actions that are bound to a specific data entity (e.g., 'CustomersV3'). bindingKind: Optional. Filter by binding type: 'Unbound' (can call directly), 'BoundToEntitySet' (operates on entity collections), 'BoundToEntityInstance' (requires specific entity key). isFunction: Optional. Filter by type: 'true' for functions (read-only), 'false' for actions (may have side-effects). Note: This filter may not be fully supported yet. limit: Maximum number of matching actions to return. profile: Configuration profile to use (optional - uses default profile if not specified)

Returns: Dictionary with matching actions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
patternYes
profileNodefault
entityNameNo
isFunctionNo
bindingKindNo
Behavior4/5

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

No annotations present, so description bears full burden. It notes that isFunction filter may not be fully supported and distinguishes between functions (read-only) and actions (may have side-effects). Returns dictionary of matching actions. Does not contradict any structured data.

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?

Well-structured with sections and examples, but contains some redundancy (search strategy repeated in pattern arg). Still concise for the amount of guidance provided.

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 no output schema, description minimally states 'Returns dictionary with matching actions'. Lacks details on pagination, error handling, or additional response fields. Adequate but could be more complete.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description adds detailed explanations for all 6 parameters including pattern (keyword search), entityName (entity filter), bindingKind (binding type), isFunction (with caveat), limit, and profile. This compensates fully for schema gaps.

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 searches for OData actions in D365 F&O using keyword-based search. It distinguishes itself from sibling tools like d365fo_search_entities by focusing specifically on actions.

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?

Provides explicit search strategy: break down requests into keywords, perform multiple searches, combine results. Includes examples and warns against complex patterns. This gives clear when-to-use guidance.

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/mafzaal/d365fo-client'

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