Skip to main content
Glama
Sign In
onepassword-mcp-server

onepassword-mcp-server

by lwsinclair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_1password_credentials

Retrieve login credentials for a specific site from 1Password vaults, enabling AI agents to log in automatically.

Instructions

Get 1Password credentials for a given site.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_name": "<item_name>"
    },
    "name": "get_1password_credentials"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The description does not disclose any behavioral traits such as what the credentials contain (e.g., username, password, other fields), whether multiple results are returned, or any authentication requirements. With no annotations, this 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.

Conciseness4/5

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

The description is a single concise sentence, front-loaded with the key action. However, given the lack of detail, it could be expanded slightly without harming conciseness.

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

Completeness2/5

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

The description fails to provide essential context such as return format (what credentials are returned), error conditions, or prerequisites. For a simple tool with one parameter, this is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter item_name is not described in the schema (0% coverage). The description mentions 'a given site' but does not explain what item_name represents (e.g., item name, site name, URL). It adds minimal additional meaning beyond the schema's title.

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 'Get 1Password credentials for a given site' clearly states the verb (Get) and resource (credentials) and specifies the scope (for a site). However, 'site' is ambiguous and could be clarified as a 1Password item or website URL.

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 on when to use this tool versus alternatives. Since there are no listed sibling tools, the description should at least indicate common use cases or prerequisites, which it does not.

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