Skip to main content
Glama
Sign In
ms-graph-dev

ms-graph-dev

by stubbedev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

graph_explain_delta

Explains Microsoft Graph delta queries to track changes efficiently, retrieving only updated items since the last synchronization.

Instructions

Explain Microsoft Graph delta queries for efficient change tracking — get only changed items since last sync rather than fetching everything.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.11

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It correctly indicates the tool is explanatory (non-destructive) but lacks details on any specific behavioral traits, such as whether it fetches data or just returns text.

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?

Single sentence with clear action ('Explain') and specific resource ('Microsoft Graph delta queries'). Front-loaded with the key benefit: 'get only changed items since last sync'. No waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless explanation tool with no output schema, the description fully covers what the tool does. It is complete given the tool's simplicity and context.

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

Parameters4/5

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

Input schema has no parameters, so schema coverage is 100%. With 0 parameters, baseline is 4. Description does not need to add parameter info.

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?

Description clearly states the tool explains Microsoft Graph delta queries for efficient change tracking. It distinguishes itself from sibling tools like graph_explain_pagination and graph_explain_odata by focusing on delta queries specifically.

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?

Description implies the tool is for understanding delta queries but does not explicitly state when to use it versus alternatives like graph_explain_pagination or graph_explain_batch. No when-not or alternative guidance is provided.

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