Skip to main content
Glama

Get Operation Result

get_operation_result

Retrieve results from asynchronous operations in Microsoft Fabric using operation IDs from 202 Accepted responses. Check operation status and access completed results for data engineering and analytics tasks.

Instructions

Get the result of a long-running operation.

Retrieves the result of an asynchronous operation using its operation ID. Operation IDs are typically returned in the x-ms-operation-id header from API calls that return 202 Accepted responses.

Parameters: operation_id: The operation ID (from x-ms-operation-id header).

Returns: Dictionary with status, operation_id, message, and operation result.

Example: ```python result = get_operation_result("12345678-1234-1234-1234-123456789abc")

if result["status"] == "success":
    operation_result = result["result"]
    # Process operation result
```

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively describes the tool's behavior: it retrieves results for long-running operations, explains where operation IDs come from (x-ms-operation-id headers), and provides a clear example of how to handle the response. It doesn't mention rate limits, authentication needs, or error conditions, but covers the core behavioral context well.

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 well-structured and appropriately sized. It starts with a clear purpose statement, provides usage context, documents the parameter, describes returns, and includes a practical code example. Every sentence adds value with zero wasted content, making it easy to scan and understand.

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?

Given the tool's moderate complexity (1 parameter, no annotations, but with output schema), the description is complete enough. It explains the purpose, usage context, parameter semantics, and includes an example showing how to handle the response. The existence of an output schema means the description doesn't need to exhaustively document return values, and it provides all necessary contextual information for effective use.

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?

The schema has 0% description coverage for its single parameter, but the description compensates by explaining that 'operation_id' comes from the x-ms-operation-id header of API calls returning 202 Accepted responses. This adds crucial semantic context beyond the bare schema, though it doesn't specify format constraints like UUID requirements.

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's purpose: 'Get the result of a long-running operation' and specifies it retrieves results for asynchronous operations using operation IDs. It distinguishes from sibling tools like 'get_job_status' by focusing on operation results rather than job status, providing specific verb+resource differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: for retrieving results of asynchronous operations where operation IDs are returned in x-ms-operation-id headers from API calls with 202 Accepted responses. However, it doesn't explicitly state when NOT to use it or mention alternatives like 'get_job_status' for job-related status checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bablulawrence/ms-fabric-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server