Skip to main content
Glama

Sign in to GovInbox

signin
Read-onlyIdempotent

Not affiliated with the U.S. government, GSA, or SAM.gov. Not a U.S. government service. Start the GovInbox sign-in flow to connect your GovInbox account. Signed-in users get 20 searches per month instead of the guest limit. This sign-in action does not consume quota.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context that signing in does not consume quota. But for an interactive auth flow it never says what actually happens — browser redirect, out-of-band user action, or returned URL — leaving the agent unsure how to complete the call. No output schema exists to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The two opening sentences are the same legal disclaimer stated twice ('Not affiliated with the U.S. government, GSA, or SAM.gov' / 'Not a U.S. government service'), which is redundant. The remaining three sentences are tight and front-load the action, so the waste is contained but real.

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?

With zero params, no output schema, and full annotation coverage, the definition is serviceable but leaves one important unknown: what the agent/user should expect after invoking an interactive sign-in flow. That is the main remaining gap given the complexity of an auth action.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The text correctly makes clear this is a parameterless action.

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?

States a specific verb and resource: 'Start the GovInbox sign-in flow to connect your GovInbox account.' No sibling tool touches authentication, so it is trivially distinguishable from the search_* / get_* family, and the title reinforces it.

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?

Gives a concrete reason to call it — signed-in users get 20 searches per month instead of the guest limit — which implicitly tells the agent when this matters (quota exhaustion). It stops short of an explicit 'call this when X, not Y' rule or naming any prerequisite/alternative.

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