Skip to main content
Glama

search

Read-only

Search Dynamics 365 Finance and Operations objects by name or keyword across pre-indexed metadata. Supports single, batch, and extension-scoped searches to locate classes, tables, forms, and more.

Instructions

Search pre-indexed D365FO objects by name or keyword. Three modes in ONE tool: • single (default) → pass query; returns name, type, model. • batch → pass queries[] (max 10) to run searches in parallel (3× faster, with dedup + cross-reference). • extensions → set scope:"extensions" to restrict to custom/ISV models only (filters out Microsoft standard code). Model names in those results are SOURCE models — never use them as create/modify targets. Use get_object_info(objectType, name) when you already know the exact name and need full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo[single] Filter by object type ("all" = no filter).all
limitNo[single|extensions] Maximum results to return
queryNo[single|extensions] Search query (class name, method name, table name, etc.). REQUIRED unless using batch `queries[]`.
scopeNo[single] Search the whole index ("all", default) or only custom/ISV models ("extensions"). Ignored when `queries[]` is provided.all
prefixNo[extensions] Extension prefix filter (e.g., ISV_, Custom_).
queriesNo[batch] Array of search queries to execute in parallel (max 10). When provided, runs in batch mode and `scope`/`query` are ignored.
verboseNo[single] Include related-searches/patterns/tips sections (off by default to keep responses compact).
deduplicateNo[batch] When true, symbols appearing in multiple query results are collapsed. Later occurrences are replaced with a reference to the query where they first appeared.
workspacePathNo[single] Optional workspace path to search local project files in addition to external metadata
crossReferenceNo[batch] Append a cross-reference summary at the end listing symbols that appeared in multiple queries. Useful for identifying the most relevant / commonly matched objects across all searches.
globalTypeFilterNo[batch] Default type filter for queries without an explicit per-query type. E.g. ["class"] restricts all untyped queries to classes. Multiple values fan out each untyped query into one search per type. Values: same as the top-level `type`, except "all" (which means "no filter" — omit this instead).
includeWorkspaceNo[single] Whether to include workspace files in search results (workspace-aware search)
Behavior5/5

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

The description adds meaningful behavioral context beyond the readOnlyHint annotation: batch mode is '3× faster', dedup and cross-reference features are disclosed, extension results carry a caveat that model names are SOURCE models and must never be used as create/modify targets. This is valuable, non-obvious behavior that annotations do not convey.

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 well-structured: a one-sentence purpose, followed by a tight bulleted list of modes and a final alternative-tool pointer. Every sentence serves a distinct purpose—no filler, and the mode-oriented structure makes the complex tool immediately scannable.

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?

The description covers the core workflow for each mode and includes performance/scope caveats. However, it only specifies the return shape for single mode ('returns name, type, model') and does not describe what batch or extensions return beyond dedup/cross-reference. Given the tool's complexity and lack of an output schema, a bit more detail on batch/extensions output would be ideal.

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?

Although the schema covers all parameters with descriptions, the tool description enriches them by mapping parameters to modes (e.g., 'pass queries[]' for batch, 'set scope:"extensions"' for extensions) and explaining high-level semantics like batch dedup and cross-reference. It clarifies the relationship between query and queries[], which is not obvious from schema alone.

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 opens with a clear, specific verb+resource statement: 'Search pre-indexed D365FO objects by name or keyword.' It enumerates three distinct modes (single, batch, extensions) and explicitly contrasts with the sibling tool get_object_info, making it easy to distinguish from alternatives.

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 guidance on when to use each mode: single for default queries, batch for parallel searches with performance benefits, extensions for filtering to custom/ISV models. It also directly recommends using get_object_info when the exact name is known and full details are needed, giving a clear when-not-to-use instruction.

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/dynamics365ninja/d365fo-mcp-server'

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