Sorsa

run_sheet_action

Trigger a function on the user's OWN connected Google Sheet by POSTing to their deployed Apps Script web app. Call get_sheet_status first; if not connected, tell them to connect their sheet in Sorsa Settings.

`action` is the name their script's doPost dispatches on (e.g. 'send_invoice',
'add_row'). `params` is a dict of values that action needs. The user's email
is always sent automatically, so the script can target the right row/recipient.

Only do what the user asked — don't invent actions or params. If you're not
sure which action name or params the user's script expects, ASK them rather
than guessing. Returns whatever the script returns.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes
`params`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the mechanism (POST to user's Apps Script web app), that the user's email is auto-attached, and that the return value is arbitrary ('Returns whatever the script returns'), implying execution of user-defined code. It doesn't cover auth requirements beyond connection state or rate/error behavior, so not 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core mechanism and precondition, then parameters and safety constraints in short paragraphs. Every sentence is purposeful; slightly longer than strictly needed but no filler.

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?

No output schema exists, and the description handles this by noting the return is script-defined; it covers preconditions, param semantics, and cautionary behavior. Missing only edge-case guidance like error handling or how to discover valid action names.

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?

Schema coverage is 0%, so the description must compensate and largely does: action is 'the name their script's doPost dispatches on' with concrete examples ('send_invoice', 'add_row'), and params is 'a dict of values that action needs'. It adds context (auto-sent email) but no format constraints for arbitrary params.

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?

States a specific verb and resource ('Trigger a function on the user's OWN connected Google Sheet by POSTing to their deployed Apps Script web app'), and clearly distinguishes this write/execute tool from its read-side sibling get_sheet_status.

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?

Explicitly gives the prerequisite ('Call get_sheet_status first; if not connected, tell them to connect their sheet in Sorsa Settings') and the escalation path ('ASK them rather than guessing'), plus a scope constraint ('Only do what the user asked').

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

All Sorsa tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?