Skip to main content
Glama

Sign in for restricted information

sign_in
Read-onlyIdempotent

Sign in with your e-mail (OAuth) to see restricted information in trust centers where you are an approved visitor. Call this when the user asks for documents or details that are shared only with approved visitors. Returns who you are signed in as and your approved trust centers.

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": "sign_in"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine value by stating the return payload (current identity plus approved trust centers), which matters because there is no output schema. However, the most important behavioral unknown is left unexplained: the tool takes zero parameters, so it is unclear how the claimed e-mail/OAuth step is actually performed (interactive browser flow? ambient session?), and no mention of expiry or re-authentication.

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?

Three tight sentences: what it does, when to call it, what it returns. No filler, and the trigger condition is front-loaded rather than buried.

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?

For a zero-parameter auth tool with no output schema, the definition covers purpose, trigger and return shape adequately. The remaining hole is the mechanics of the OAuth/identity step, which is the one thing an agent cannot infer from an empty schema.

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?

With zero parameters the baseline would normally be 4, but the description asserts an input — "Sign in with your e-mail" — that has no corresponding schema property, creating a real ambiguity about where that e-mail comes from. That mismatch is the sort of thing a description should resolve rather than introduce.

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?

States a concrete verb (sign in) plus the resource/scope it unlocks (restricted information in trust centers as an approved visitor). It is specific enough to separate this authentication tool from the list_*/get_* siblings that fetch content once authorized, though it never names those siblings explicitly.

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?

"Call this when the user asks for documents or details that are shared only with approved visitors" gives a clear trigger condition tied to restricted content. What is missing is the inverse rule — that the tool is not needed for public trust-center data — and any note about already being signed in.

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