Skip to main content
Glama
mafzaal

Dynamics 365 Finance & Operations MCP Server

by mafzaal

d365fo_search_entities

Search for Dynamics 365 Finance & Operations data entities by keyword, with filters for category, OData access, and Data Management Framework support.

Instructions

Search for D365 F&O data entities using simple keyword-based search.

IMPORTANT: When a user asks for something like "Get data management entities" or "Find customer group entities", break the request into individual keywords and perform MULTIPLE searches, then analyze all results:

  1. Extract individual keywords from the request (e.g. "data management entities" → "data", "management", "entities")

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

  3. Combine and analyze results from all searches

  4. Look for entities that match the combination of concepts

SEARCH STRATEGY EXAMPLES:

  • "data management entities" → Search for "data", then "management", then find entities matching both concepts

  • "customer groups" → Search for "customer", then "group", then find intersection

  • "sales orders" → Search for "sales", then "order", then combine results

Use simple keywords, not complex patterns. The search will find entities containing those keywords.

Args: pattern: Simple keyword or text to search for in entity names. Use plain text keywords, not regex patterns. For multi-word requests like 'data management entities': 1) Break into keywords: 'data', 'management' 2) Search for each keyword separately: 'data' then 'management' 3) Run separate searches for each keyword 4) Analyze combined results. Examples: use 'customer' to find customer entities, 'group' to find group entities. entity_category: Filter entities by their functional category (e.g., Master, Transaction). data_service_enabled: Filter entities that are enabled for OData API access (e.g., for querying). data_management_enabled: Filter entities that can be used with the Data Management Framework (DMF). is_read_only: Filter entities based on whether they are read-only or support write operations. limit: Maximum number of matching entities to return. Use smaller values (10-50) for initial exploration, larger values (100-500) for comprehensive searches. profile: Configuration profile to use (optional - uses default profile if not specified)

Returns: Dictionary with matching entities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
patternYes
profileNodefault
is_read_onlyNo
entity_categoryNo
data_service_enabledNo
data_management_enabledNo
Behavior3/5

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

With no annotations provided, the description explains the keyword-based search behavior and the multi-search logic. It does not disclose performance characteristics, case sensitivity, or what happens with empty results.

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 front-loaded with the main purpose and then provides detailed usage instructions. While slightly verbose, every section adds useful context, and the structure is well-organized.

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 complexity and lack of output schema, the description adequately covers the search logic. However, it omits details about return values beyond a vague 'dictionary', and does not discuss error handling or edge cases.

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 0%, so the description must compensate. It provides good detail for the required 'pattern' parameter and limited guidance for 'limit', but other parameters like entity_category and is_read_only get only minimal descriptions.

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

Purpose4/5

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

The description clearly identifies the tool as searching for D365 F&O data entities via keyword-based search. However, it does not explicitly differentiate from the sibling tool d365fo_query_entities, which may cause confusion.

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?

Provides detailed instructions on when to use the tool, including a multi-search strategy for multi-word queries. However, it lacks guidance on when not to use it and does not mention alternative tools like d365fo_query_entities.

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