Skip to main content
Glama
Sign In
google-classroom-mcp

google-classroom-mcp

by alanmagno1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_profile

Verify your Google Classroom connection and retrieve the authenticated user profile for your accounts, including the specified account.

Instructions

Verifica la conexión y devuelve el usuario autenticado de cada cuenta (o de la indicada).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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 tool verifies connectivity and returns authenticated user data, and that it can operate per account. However, it does not mention side effects, authentication requirements, error behavior, or what happens when no account is available.

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?

A single, front-loaded sentence communicates the core purpose and the parameter behavior without redundancy. Every part of the sentence contributes useful information.

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

Completeness3/5

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

Given the low parameter count and simple input schema, the description is minimally viable. It tells the agent what the tool does and how the optional account affects behavior. However, with no output schema and no annotations, the lack of detail about the returned user object and connection-check semantics leaves some gaps.

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 0%, so the description must clarify the account parameter. The phrase 'de cada cuenta (o de la indicada)' indicates that the optional account parameter selects a specific account, with the default covering all accounts. This adds meaningful semantic value, though it stops short of explaining accepted formats or values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: verify the connection and return the authenticated user for each account (or a specified one). The verb-resource pair is specific and distinct from the sibling tools, though it does not explicitly contrast with any sibling.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as list_accounts or get_course_contents. The tool's use case can be inferred, but the description does not state explicit conditions or exclusions.

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