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

ms-graph-dev

by stubbedev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

graph_explain_pagination

Explains pagination in Microsoft Graph API: using @odata.nextLink to iterate all result pages.

Instructions

Explain how Microsoft Graph API pagination works with @odata.nextLink, and how to iterate all pages of results.

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_pagination"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.11

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, but the description accurately conveys the tool's informational nature and lack of side effects. It transparently describes the content (pagination explanation) without misleading the agent. However, it could mention the return format or that it does not trigger API calls.

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 sentence that is clear, direct, and contains no extraneous words. It is front-loaded with the main purpose and is appropriately concise for the tool's simplicity.

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?

Given the tool has no parameters or output schema, the description is sufficient to convey its purpose. However, it does not mention what the explanation looks like (e.g., text, format), which could be helpful but is not critical. The presence of multiple sibling explain tools suggests a bit more context could be beneficial.

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?

There are zero parameters, and the schema coverage is trivially 100%. The description correctly omits parameter details since none exist. It adds no extra semantic information beyond the schema, but none is needed.

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 explains Microsoft Graph API pagination with specific detail about @odata.nextLink and iterating results. The verb 'explain' and resource are explicit, and it distinguishes from sibling explain tools by focusing on pagination.

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?

The description only states what the tool does, with no guidance on when to use it versus sibling tools like graph_explain_odata. It does not provide context for choosing this tool over alternatives, limiting its helpfulness for an AI agent deciding which tool to invoke.

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