PowerPlatform MCP Server

query-records

Query records in Dataverse by providing an entity name and an OData filter expression. Optionally set a maximum number of records to return.

Instructions

Query records using an OData filter expression

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": {
      "entityNamePlural": "<entityNamePlural>",
      "filter": "<filter>"
    },
    "name": "query-records"
  }
}

Input Schema

Name	Required	Description
`filter`	Yes	OData filter expression (e.g., "name eq 'test'" or "createdon gt 2023-01-01")
`maxRecords`	No	Maximum number of records to retrieve (default: 50)
`entityNamePlural`	Yes	The plural name of the entity (e.g., 'accounts', 'contacts')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.5Jul 31, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'query records' and does not mention whether the operation is read-only, how pagination works, what happens on invalid filters, or what the return format looks like. This is minimal disclosure for a query 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, clear sentence that directly states the tool's purpose with no filler or redundancy. It is appropriately sized for the tool's simplicity and front-loads the key action.

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?

The tool is relatively simple with 3 parameters and no output schema. However, the description does not clarify what the query returns (e.g., a list of records) or how maxRecords and pagination behave, which would be helpful. Given the high schema coverage and straightforward nature, this is adequate but not complete.

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?

The schema provides 100% coverage with descriptions for all three parameters, including examples for the filter expression. The description's mention of 'OData filter expression' adds no new meaning beyond the schema. Baseline 3 is appropriate because the schema does the heavy lifting.

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 function: 'Query records using an OData filter expression'. The verb 'query' plus the resource 'records' makes the action specific, and it naturally distinguishes from sibling tools like get-record (single record retrieval) and metadata tools.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention scenarios such as filtering a list, nor does it exclude cases like single-record lookup. The only clue is the name and the OData filter mention, which is implicit rather than explicit.

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

Deploy Server