Skip to main content
Glama

Can the bot open this Google Sheet or Calendar

dosai_check_google_access

Check that the bot's Google address really has access to the owner's sheet or calendar BEFORE creating a function on it. For a sheet returns its tabs and columns, for a calendar the nearest events. If access is missing the answer says what the owner must do. 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>",
      "kind": "<kind>"
    },
    "name": "dosai_check_google_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
project_idYesFrom dosai_list_projects.
sheet_nameNoFor sheets: a tab name; omit for the first tab.
calendar_idNoFor calendar: the calendar's id, usually its Gmail address.
spreadsheetNoFor sheets: the sheet's link or id.

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.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses what the response contains (tabs and columns for sheets, nearest events for calendars) and what happens on failure ('the answer says what the owner must do'). The remaining gap is that it never explains the surprising readOnlyHint=false for what reads like a verification call, nor whether the check has side effects.

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?

Three compact sentences with the timing constraint front-loaded and no filler. Phrasing like 'For a sheet returns its tabs and columns' is slightly telegraphic, but nothing is wasted.

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?

With no output schema, the description does the work of describing the return shape (tabs/columns, nearest events) and the failure mode, which is the right coverage for a 5-parameter check tool. It could be stronger on which parameters are conditionally required per kind.

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 description coverage is 80%, so the schema already explains project_id, sheet_name, calendar_id and spreadsheet. The description only adds the high-level branching (sheets vs calendars) that the enum already conveys, without clarifying the sheet/calendar conditional requirements or the 'omit sheet_name for the first tab' behavior.

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 ('check that the bot's Google address really has access to the owner's sheet or calendar') and bounds the scope to a pre-flight verification. It also distinguishes itself from the family of dosai_* connection/creation tools by tying the check to 'BEFORE creating a function on it.'

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?

Gives explicit timing guidance ('BEFORE creating a function on it') and a prerequisite ('Requires editor role'), which is exactly the condition an agent needs to decide to call it. It does not name an alternative tool for the post-creation case, so it stops short of a full when/when-not routing statement.

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