Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

clear_server_cache

Clears cached metadata and authentication tokens and invalidates query continuations when stale local state causes Dynamics 365 connection or query issues; CRM data is unchanged.

Instructions

Clear local cached metadata and authentication tokens and invalidate query continuations. Does not change CRM data.

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": "clear_server_cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does useful work by disclosing what is discarded and that CRM data is untouched, but it omits the most consequential side effect: clearing authentication tokens likely forces re-authentication, and it doesn't say whether the clear is per-session or affects the whole environment, or whether in-flight queries fail.

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?

Two short sentences, front-loaded with the action and its targets, followed immediately by the scope disclaimer. Nothing is wasted and there is no filler.

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?

For a low-complexity, single-optional-parameter tool with no output schema, this is close to sufficient. However, the post-call state (re-authentication requirement, whether cached data must be refetched) is the main thing an agent would need and is absent.

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 100% and the single parameter (environment_profile) is fully documented in the schema as an optional profile override. The description says nothing about it, adding no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and effect set: clearing cached metadata and auth tokens plus invalidating query continuations. The negative scope clause ('Does not change CRM data') sharpens the boundary, and no sibling tool performs anything similar, so confusion risk is low. It stops short of 5 only because 'local' vs. the tool name's 'server' leaves the cache location slightly ambiguous.

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?

There is no explicit trigger for when to call this (e.g., after metadata changes, stale schema reads, or expired tokens), nor any stated alternative. The 'does not change CRM data' clause implies a safe/diagnostic role, but the agent must infer the invocation context. Usage is implied rather than guided.

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