fix: OAuth scope filtering to respect enabled tools filter (#153)

* fix: only add scopes of enabled tools

* refac: formatting

---------

Co-authored-by: Cagri Canbol <c.canbol@dhbbank.com>

feat: hello hack; allow polymorphic attachment properties by updating…

… object schema to passthrough for microsoft_graph_attachment (#151)

feat: fix release build (hopefully) (#150)

fix: add support for auto-returning download URLs for specific endpoi…

…nts helping agent not sending whole file to LLM (#142)

feat: add findMeetingTimes endpoint with Calendars.Read.Shared ORG-MO…

…DE scope (#143)

fix: correct SharePoint file download endpoint path (#139)

Fixes #137 - download-onedrive-file-content was returning 404 for SharePoint files

Root cause: The endpoint path pattern included an incorrect `/children/{driveItem-id1}`
segment that doesn't match the Microsoft Graph API specification.

Changed from:
/drives/{drive-id}/items/{driveItem-id}/children/{driveItem-id1}/content

To correct path:
/drives/{drive-id}/items/{driveItem-id}/content

Tested with SharePoint Internal site - file downloads now work correctly.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <noreply@anthropic.com>

feat: add excludeResponse parameter to reduce token usage (#136)

Added an optional excludeResponse parameter to all MCP tools that allows
excluding the full response body from Microsoft Graph API and only
returning a success/failure indication.

This is useful for operations where only the outcome matters (success or
failure) and the response data is not needed, significantly reducing
token usage in MCP responses.

Changes:
- Added excludeResponse parameter to all tool schemas (default: false)
- Updated GraphRequestOptions interface to include excludeResponse
- Modified formatJsonResponse to return minimal response when enabled
- Added error handling to return { success: false } for failures

Behavior:
- excludeResponse=false (default): Returns full response as before
- excludeResponse=true (success): Returns { "success": true }
- excludeResponse=true (error): Returns { "success": false } with isError: true

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <noreply@anthropic.com>

fix: ensure retried requests go through full error handling and parsi…

…ng (#135)

When a 401 error occurs and the token is refreshed, the retry request
was bypassing all error handling (403, 404, etc.) and JSON parsing by
returning early. This fix ensures the retried response flows through
the same error checking and parsing logic as the initial request.

Changes:
- Changed `response` from const to let to allow reassignment
- Changed retry logic to reassign response instead of returning early

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <noreply@anthropic.com>

fix: prevent infinite recursion in mergeAllOfSchemas by tracking visi…

…ted schemas - hope this works (#132)

fix: update the parameter handling by adding auto-correction for nest…

…ed fields in request body (#131)

This is kind of a hack, as it doesn't actually fix the generated schema - BUT it _should_ work.
My theory is that some agents might get confused with body in body, and this solves that problem.