show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
NotebookLM
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool shows platform and adapter versions, which aligns with these traits. No contradiction, and the description adds useful context beyond annotations.
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 a single, well-formed sentence with no unnecessary words. Every word earns its place.
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 parameterless, read-only tool with no output schema, the description is complete. It clearly communicates the tool's purpose without needing additional detail.
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?
There are no parameters (schema description coverage 100%), so the description does not need to explain parameters. A baseline of 4 is appropriate.
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 clearly states the verb 'Show' and specifies what is shown: current MCP platform and adapter versions. This distinguishes it from siblings like toolkit_info, which likely provides different info.
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 use when version info is needed, but does not explicitly state when to use or alternatives. Given the tool's simplicity and lack of similar siblings, this is adequate but not exemplary.
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.
TDQS
B3.2/5.0
Disambiguation4/5
Most tools have clearly distinct purposes (notebook vs source vs note vs artifact vs sharing). Minor overlap exists between notebooklm_ask and notebooklm_history (both Q&A-related) and between artifact generate/poll/retry, but descriptions help differentiate. Meta-tools like marketplace and authenticate are separate in function.
Naming Consistency3/5
Core tools follow a consistent notebooklm_{resource}_{action} pattern. However, meta-tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) lack the notebooklm_ prefix, breaking overall naming consistency. Within the core domain, naming is predictable.
Tool Count3/5
43 tools is high but covers a broad domain: notebooks, sources, notes, artifacts (multiple types), sharing, Q&A, plus meta-tools. Some tools could be merged (e.g., share_add/remove/update/view_level), and meta-tools inflate count. Feels slightly heavy but not excessive for the feature set.
Completeness4/5
Covers full lifecycle for notebooks, sources, notes, artifacts (CRUD plus generate, download, poll, retry, suggestions). Sharing and Q&A have comprehensive operations. Minor gap: no tool to update notebook metadata beyond rename, but overall very complete.