Skip to main content
Glama

osirAgentList

Read-onlyIdempotent

osirAgentList: List the AI agents (e.g. Hermes) the user has installed on their own VPS, with their ids and dashboard URLs. Requires authentication.

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

Input Schema

NameRequiredDescriptionDefault
sessionKeyNoSession key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new context: the auth prerequisite and the shape of the payload (ids plus dashboard URLs), which annotations do not convey.

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?

One tight sentence with the scope and return value front-loaded and no filler. The only waste is the redundant 'osirAgentList:' prefix that merely restates the name.

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 simple read-only list with full schema coverage and no output schema, the description covers what it does, the auth prerequisite, and what comes back. Nothing an agent needs in order to call it correctly is missing, though the absence of any per-agent alternative leaves a small routing gap.

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?

Schema coverage is 100% and the single sessionKey parameter is documented in detail, including when to omit it for OAuth connections. The description contributes nothing beyond the schema here, so the baseline 3 applies.

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 specific verb and resource ('List the AI agents') plus scope ('installed on their own VPS') and return contents ('ids and dashboard URLs'), with a concrete example (Hermes) that pins down what an agent is. It never names a sibling such as osirAgentStatus, so the differentiation relies on the tool names alone rather than explicit text.

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 only explicit guidance is the prerequisite 'Requires authentication', which is useful. There is no statement of when to prefer this over osirAgentStatus (per-agent detail) or when it is not appropriate, so the agent must infer the boundary from the sibling names.

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.