Skip to main content
Glama
Sign In
Microsoft Fabric MCP Server

Microsoft Fabric MCP Server

by og-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

fabric_get_report

Read-only

Get a report from Microsoft Fabric by providing its ID. Optionally include a workspace ID to retrieve the report from a specific workspace.

Instructions

Get a report by ID.

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": {
      "reportId": "<reportId>"
    },
    "name": "fabric_get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportIdYesReport ID
workspaceNoWorkspace ID (defaults to FABRIC_DEFAULT_WORKSPACE)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The description does not contradict the readOnlyHint annotation. However, it adds no extra behavioral context beyond what the annotation already provides. With annotations present, a score of 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence. It is appropriately concise, though it could benefit from a brief note on usage or return value.

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 simple get tool with no output schema, the description is minimally adequate. It tells the agent the basic function but lacks context about the report object or return format.

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 coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no additional meaning or clarification beyond the schema.

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?

The description 'Get a report by ID' clearly states the action (get) and resource (report) with a specific input (ID). It is distinct enough from siblings like fabric_get_item, though it does not highlight the unique aspects of reports.

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?

No guidance is provided on when to use this tool versus alternatives such as fabric_list_reports or other get_* tools. The agent receives no context for selection.

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