getLoginLink
Get a login link to authenticate and manage your tokens
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
BlogCaster MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears the full burden. It states the tool gets a login link but does not disclose whether it has side effects (e.g., invalidating tokens), requires specific permissions, or what the returned link contains. This lack of behavioral detail is a significant gap.
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, concise sentence that delivers the essential purpose without redundancy. Every word contributes to understanding the tool's function.
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?
For a simple tool with no parameters, the description is adequate but not fully complete. It implies a return value (a login link) but does not describe any caveats, such as token expiration, usage limits, or authentication prerequisites. Given there is no output schema, more context would be beneficial.
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?
The tool has zero parameters, and the schema description coverage is 100% with no properties. Per the rubric, a baseline of 4 is appropriate since there are no parameters that need semantic explanation.
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 uses a specific verb 'Get' with a clear resource 'login link' and states its purpose ('authenticate and manage your tokens'). This distinguishes it from sibling tools like deletePost, getBlogs, and whoami, which focus on other resources.
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 for authentication and token management, but it doesn't explicitly state when to use this tool vs alternatives like logout or whoami. There is no direct guidance on context or exclusions, so it only meets the 'implied usage' level.
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
C2.3/5.0
Disambiguation5/5
Each tool targets a distinct concern: authentication (getLoginLink, logout, whoami) and blog post management (publishPost, updatePost, deletePost, getBlogs). No two tools appear to overlap in purpose, so an agent can easily select the right one based on the action needed.
Naming Consistency3/5
All tool names use camelCase, but the structural pattern is inconsistent: most are verb_noun (deletePost, getBlogs), while 'logout' is a single verb and 'whoami' is a command-style name. The mixed conventions, though readable, reduce predictability.
Tool Count5/5
With 7 tools, the server is well-scoped for a blog management service. It covers both authentication and core post operations without excessive redundancy, fitting comfortably within the ideal 3-15 range.
Completeness2/5
The server provides create (publishPost), update, and delete for posts, but lacks any read/list operation for posts other than getBlogs, which focuses on blogs rather than individual posts. This is a significant gap for a blogging platform, as agents cannot retrieve existing posts to view or edit them.