Skip to main content
Glama

List login profiles

list_profiles
Read-only

Lists configured login profiles with name, root URL, and username so you can choose the right profile for login. Passwords are never returned.

Instructions

Lists the configured login profiles: name, root URL and username. Passwords are never returned. Use it to pick a profile for login.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value on top by disclosing the returned fields and the security-relevant constraint that passwords are never returned. It does not cover ordering, empty-list behavior, or whether profiles come from a local config file, but the key behavioral surprises are disclosed.

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?

Two short sentences: the first states what is returned, the second states the purpose and next step. The security caveat is placed where it matters and no sentence is redundant.

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

Completeness5/5

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

With no input parameters and no output schema, the description carries the return-value burden and does so by enumerating the fields returned and ruling out passwords. Combined with the read-only annotations, an agent has everything needed to call this and use the result correctly.

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 takes no parameters, so per the baseline this dimension starts at 4. Nothing in the description is needed to disambiguate inputs, and it correctly does not invent any.

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?

Names a specific verb and resource ("Lists the configured login profiles") and enumerates exactly what each entry contains (name, root URL, username), so the agent knows what it gets back. It does not explicitly contrast itself with the sibling `login_status`, which is the closest thing to an overlap, so it stops just short of full sibling differentiation.

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?

"Use it to pick a `profile` for `login`" gives concrete when-to-use guidance and chains this tool to the correct follow-up call. There is no explicit when-not guidance or prerequisite note, but for a zero-parameter listing tool the usage context is clear enough to act on.

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