Skip to main content
Glama

Connect a price list from a Google Sheet

dosai_connect_price_sheet
Destructive

Read the owner's price list from a Google Sheet link and save it as a draft. Before calling, the owner shares the sheet with the bot's Google address (dosai_list_function_templates returns it). Then look at the draft with dosai_get_price_list and switch it on with dosai_manage_price_list (activate); a working sheet price is re-read every 15 minutes. Requires editor role.

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": {
      "project_id": "<project_id>",
      "url": "<url>"
    },
    "name": "dosai_connect_price_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLink to the Google Sheet.
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the import lands in a non-live draft state, that activation is a separate deliberate step, that a live sheet price is re-read every 15 minutes, and that an editor role plus an external sharing setup are required. These are exactly the operational facts an agent needs before invoking an openWorld, destructive-hinted write.

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?

Four short sentences, front-loaded with the action, then prerequisites, then the follow-up chain. Every sentence carries information; the only mild weakness is that the 'Requires editor role' constraint is appended at the end rather than grouped with the other preconditions.

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?

For a two-parameter write tool with no output schema, the description covers what is created (a draft), what it is not (not live), how it becomes live, how often data refreshes, and what access is needed. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100% and both parameters are documented in-schema, so the description need not restate them. It adds only indirect meaning about the url parameter (it must be a sheet shared with the bot address) and says nothing specific about project_id beyond the schema's own pointer to dosai_list_projects.

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 opens with a specific verb and resource: 'Read the owner's price list from a Google Sheet link and save it as a draft.' It also distinguishes this tool from the related read/activate tools (dosai_get_price_list, dosai_manage_price_list) that operate on the resulting draft.

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?

It spells out a prerequisite step before calling (owner must share the sheet with the bot's Google address, obtained from dosai_list_function_templates), then the exact follow-up sequence (inspect with dosai_get_price_list, activate with dosai_manage_price_list). It also states an eligibility condition ('Requires editor role'), so the agent knows when it cannot use this tool.

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