Skip to main content
Glama

Set Login URIs

keychain_set_login_uris

Configure or modify URIs and match types for a login item in your vault, using replace or merge modes to manage access rules.

Instructions

Set or update the URIs (and per-URI match types) for a login item. mode=replace overwrites; mode=merge updates/adds by uri.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
modeNo
urisYes
revealNo

Implementation Reference

  • Tool registration and handler implementation for 'keychain_set_login_uris' in src/tools/registerTools.ts.
      `${deps.toolPrefix}.set_login_uris`,
      {
        title: 'Set Login URIs',
        description:
          'Set or update the URIs (and per-URI match types) for a login item. mode=replace overwrites; mode=merge updates/adds by uri.',
        inputSchema: {
          id: z.string(),
          mode: z.enum(['replace', 'merge']).optional(),
          uris: z.array(
            z.object({
              uri: z.string(),
              match: uriMatchInputSchema.optional(),
            }),
          ),
          reveal: z.boolean().optional(),
        },
        _meta: toolMeta,
      },
      async (input, extra) => {
        if (isReadOnly) return readonlyBlocked();
        const sdk = await deps.getSdk(extra.authInfo);
        const updated = await sdk.setLoginUris({
          id: input.id,
          mode: input.mode,
          uris: normalizeUrisInput(input.uris) ?? [],
          reveal: effectiveReveal(input),
        });
        return {
          structuredContent: { item: updated },
          content: [{ type: 'text', text: 'Updated.' }],
        };
      },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool's mutating behavior ('Set or update') and the effect of 'mode', but fails to address critical aspects like required permissions, whether changes are reversible, error handling, or rate limits. This leaves significant gaps for a mutation tool.

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 front-loaded and efficiently structured in two sentences: the first states the purpose, the second clarifies parameter behavior. Every word earns its place, with no redundancy or fluff.

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?

For a mutation tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on permissions, side effects, error cases, and the meaning of 'reveal'. While concise, it doesn't provide enough context for safe and effective use.

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?

Given 0% schema description coverage, the description compensates well by explaining the semantics of the 'mode' parameter ('replace overwrites; mode=merge updates/adds by uri') and implying 'uris' includes 'per-URI match types'. It doesn't cover 'id' or 'reveal', but adds meaningful context beyond the bare schema.

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 clearly states the verb ('Set or update') and resource ('URIs for a login item'), making the purpose specific and understandable. It distinguishes from siblings like 'keychain_create_login' (creation) and 'keychain_update_item' (general update), though it doesn't explicitly name alternatives.

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 by explaining the 'mode' parameter behavior ('replace overwrites; merge updates/adds'), which suggests when to use each mode. However, it lacks explicit guidance on when to choose this tool over siblings like 'keychain_update_item' or prerequisites for the 'id' parameter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/icoretech/warden-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server