Skip to main content
Glama
Sign In
Microsoft Fabric MCP Server

Microsoft Fabric MCP Server

by og-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

fabric_list_spark_custom_pools

Read-only

List custom Spark pools in a workspace to view available compute resources for Spark workloads.

Instructions

List the custom Spark pools in a workspace.

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

Input Schema

NameRequiredDescriptionDefault
workspaceNoWorkspace ID (defaults to FABRIC_DEFAULT_WORKSPACE)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotation readOnlyHint=true already informs the agent it's a safe read operation. The description adds that it lists 'custom' pools, but does not disclose any additional behaviors (e.g., whether it returns names, details, or pagination).

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, concise sentence that directly states the tool's function without any unnecessary words or structure issues.

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?

The description is minimal and lacks information about the output format (e.g., what fields are returned for each pool). With no output schema, the agent has no details about the response structure.

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?

The one parameter 'workspace' is fully described in the schema (with a default value). The description does not add any additional meaning beyond what the schema provides, so baseline 3 applies.

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 uses specific verb 'List' and resource 'custom Spark pools' within a workspace. It clearly distinguishes from sibling tools like fabric_list_spark_job_definitions or fabric_list_livy_sessions, which list different resources.

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 on when to use this tool versus alternatives, no prerequisites or scope mentioned beyond the workspace parameter. The description simply states the action without context.

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