Skip to main content
Glama
Sign In
Microsoft Graph MCP Server

Microsoft Graph MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_table

Create an Excel table from a specified cell range in a file. Provide file ID and range address such as 'A1:D10' to structure data with optional headers.

Instructions

Create a table from a range. address: e.g. 'A1:D10'.

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": {
      "file_id": "<file_id>",
      "address": "<address>"
    },
    "name": "create_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
file_idYes
has_headersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It states that a table is created, but does not explain side effects, whether headers are inferred, whether an existing table is replaced, what happens on failure, or what the response contains.

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 extremely concise and front-loaded, with a single clear action sentence followed by a useful address example. There is no filler or repetition of schema data.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three parameters, no annotations, and no output schema, this description is too sparse. It omits the meaning of half the parameters, gives no return-value expectations, and provides no behavior or preconditions, leaving an agent to guess important invocation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description needed to clarify all parameters. It only explains 'address' with an example ('A1:D10'), which is helpful, but it says nothing about 'file_id' or 'has_headers' beyond their schema titles and default.

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 uses a specific verb ('Create') and resource ('a table from a range'), making the core action clear. It is distinguishable from the many sibling tools because it names both the operation and the spreadsheet concept, though it does not explicitly mention file context beyond the address.

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?

There is no guidance on when to use this tool versus alternatives like list_tables, append_table_row, or update_table_row. The description implies the usage only through the verb 'create' but provides no exclusions or contextual selection criteria.

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