Skip to main content
Glama
Sign In
google-workspace-mcp-advanced

google-workspace-mcp-advanced

by Skeptomenos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_form_response

Retrieve a single form response by its ID. Get answer details and metadata for any Google Form response.

Instructions

Get one response from the form.

Args: user_google_email (str): The user's Google email address. Required. form_id (str): The ID of the form. response_id (str): The ID of the response to retrieve.

Returns: str: Response details including answers and metadata.

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": {
      "user_google_email": "<user_google_email>",
      "form_id": "<form_id>",
      "response_id": "<response_id>"
    },
    "name": "get_form_response"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYes
form_idYes
response_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.10

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the operation retrieves a response and returns details, implying a read-only operation, but does not explicitly state there are no side effects, error behavior, or auth requirements. The 'Returns' line adds some context but is limited.

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 concise and well-structured with a clear one-line summary followed by Args and Returns sections. Every sentence is purposeful, and it avoids redundancy with the schema.

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?

Given the tool's simplicity (3 required parameters) and the presence of an output schema, the description is reasonably complete. It conveys the core operation and return type, though it omits potential error cases or format specifics, which are likely covered by the output schema.

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 description coverage is 0%, but the description lists all three parameters with meaningful explanations: user_google_email, form_id, and response_id. It clarifies the role of each parameter and marks user_google_email as Required, adding value beyond the bare schema.

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 'Get one response from the form' with a specific verb and resource, clearly distinguishing it from sibling tools like list_form_responses and get_form. The phrase 'one response' clarifies it retrieves a single response by ID.

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

Usage Guidelines3/5

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

The description implies usage by requiring response_id, but does not explicitly mention when to use this over list_form_responses or other alternatives. No exclusionary guidance is provided, leaving the agent to infer the distinction from the word 'one'.

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

Deploy Server

Other Tools