Skip to main content
Glama

Quadratic

by io.github.quadratichq

auth

Destructive

Authenticate the MCP session with Quadratic.

Actions: • login() — Start an OAuth device authorization flow. Returns a URL the user must open in a browser to authorize. The flow is completed by confirm_login. • confirm_login(device_code) — Complete an in-progress login by polling for user authorization. If the response indicates the user has not yet authorized, this action can be called again with the same device_code to continue polling. confirm_login is idempotent: if a later tool call reports "Not authenticated on this connection", call confirm_login again with the same device_code to re-establish auth (some clients use a new session per request, so the session that ran the tool may differ from the one that logged in). • set_token(token, email?) — Set a JWT directly (used when the OAuth device flow is not available). • logout() — Clear saved authentication for the current session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: login, confirm_login, set_token, or logout
paramsNoParameters for the action (see tool description)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

The description richly discloses behavior beyond annotations: login returns a URL, confirm_login is idempotent and can be polled repeatedly, set_token directly sets a JWT, and logout clears saved auth. It also explains the nuance that some clients use new sessions per request, which is critical for effective use. This does not contradict the annotations (destructiveHint=true aligns with logout; idempotentHint=false is clarified per-action).

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 with a short opening sentence followed by a bulleted list of actions. Each bullet is concise, information-dense, and directly relevant. No fluff or repetition; every sentence contributes to understanding.

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 complexity (multiple actions, async polling, session nuances) and the generic schema, the description is remarkably complete. It covers all actions, their parameters, step-by-step flow, idempotent behavior, and error recovery. No output schema exists, but the description clarifies expected inputs and key outputs like the login URL.

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

Parameters5/5

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

The input schema only provides generic 'action' and 'params' fields. The description compensates fully by specifying the arguments for each action: login() takes no params, confirm_login(device_code) requires a device code, set_token(token, email?) takes a token and optional email, and logout() takes none. This is essential guidance that the schema does not provide.

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 states 'Authenticate the MCP session with Quadratic'—a specific verb and resource. It then enumerates four distinct actions (login, confirm_login, set_token, logout), making the tool's purpose unambiguous and clearly distinct from sibling file/data tools.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided for each action: use login for OAuth device flow, confirm_login to complete/poll authorization, set_token when OAuth is unavailable, and logout to clear auth. It also instructs when to re-call confirm_login (on 'Not authenticated' errors) due to session differences, offering concrete when-to-use and alternative guidance.

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

All Quadratic toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a clearly distinct concern: auth handles session lifecycle, files_read lists metadata, files_write manages file sessions, read_data queries spreadsheet contents, and write_data modifies them. No two tools have overlapping purposes.

Naming Consistency2/5

Tool names follow inconsistent conventions: 'auth' is a bare noun, 'files_read' and 'files_write' use noun_verb order, while 'read_data' and 'write_data' use verb_noun order. This mixed pattern makes it harder to predict related tool names.

Tool Count5/5

Five top-level tools form an elegant umbrella structure that groups dozens of actions into meaningful categories. The count is ideal for guiding an agent to the correct tool without overwhelming it.

Completeness4/5

The surface covers the full spreadsheet lifecycle: authentication, file management, cell/range operations, formulas, code, SQL, formatting, sheets, tables, charts, pivot tables, validation, and history. Missing file deletion/rename and some advanced sheet management are minor gaps that can be worked around.

Resources