Skip to main content
Glama

Explain and translate a spreadsheet formula

explain_formula
Read-only

Explains an Excel or Google Sheets formula in plain English and returns the equivalent in Excel, Google Sheets, SQL and pandas, with common pitfalls. Use when the user has a specific formula they do not understand or want to move to another tool.

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": {
      "formula": "<formula>"
    },
    "name": "explain_formula"
  }
}

Input Schema

NameRequiredDescriptionDefault
formulaYesThe formula, starting with =, exactly as it appears in the cell.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=true), so the description's job is to add behavioral context, and it does by disclosing the shape of the response: four target dialects plus pitfalls. With no output schema, that disclosure is genuinely load-bearing. It does not mention limits on formula complexity, unsupported functions, or whether translation is best-effort, which keeps it from a 5.

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?

One sentence plus one usage sentence, zero filler, and the highest-value information (what it returns: four dialects and pitfalls) is front-loaded before the usage clause. Nothing could be removed without losing signal.

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

Completeness4/5

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

For a one-parameter, read-only tool with a fully described schema and no output schema, the definition covers purpose, trigger, and return shape adequately. The only residual gap is the absence of any caveat about unsupported or dialect-specific functions, which would matter for an open-world translation tool.

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?

There is a single parameter and schema description coverage is 100%, including the valuable instruction that the formula must start with '=' and match the cell exactly. The description adds no format or edge-case detail beyond what the schema already says, so the baseline of 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 states a specific verb and resource ('Explains an Excel or Google Sheets formula') and then enumerates the exact artifacts produced: plain-English explanation, Excel/Google Sheets/SQL/pandas equivalents, and common pitfalls. That output enumeration distinguishes it from the sibling search_formula_library, which by name suggests lookup rather than per-formula explanation.

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?

It gives an explicit trigger condition: 'Use when the user has a specific formula they do not understand or want to move to another tool,' which covers both the explain and translate intents. It stops short of naming alternatives or stating when not to use it (e.g., bulk formula auditing), so it is clear context without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources