Skip to main content
Glama

osirAppList

Read-onlyIdempotent

osirAppList: List the authenticated user's deployed Osir apps with their live URLs and status. An entry with kind 'agent' is a ready-made AI agent (e.g. Hermes): manage it with the osirAgent* tools, never the osirApp* ones. 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": "osirAppList"
  }
}

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. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the authentication requirement and the mixed-content gotcha (agent entries appearing in an app listing), which is real value. It stops short of describing result shape, ordering, or volume, so it is additive but not rich.

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?

Three short sentences: purpose first, the critical agent-vs-app routing second, the auth requirement last. No restated field names, no filler.

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 read-only list tool with no output schema, the description covers purpose, return content, auth, and the sibling-routing trap an agent would otherwise fall into. Minor gaps remain around result volume/ordering and the other possible values of kind beyond 'agent'.

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?

With schema description coverage at 100% and a single optional sessionKey parameter fully documented in the schema, the description is not required to explain it. It never mentions sessionKey, so it adds nothing beyond the schema; the baseline 3 applies.

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 ("List the authenticated user's deployed Osir apps") and adds the scope of what comes back ("live URLs and status"). It also explicitly draws the boundary against the osirAgent* family, so an agent can separate this from the many osirApp* siblings without opening their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit conditional routing rule: entries with kind 'agent' must be managed with osirAgent* tools, "never the osirApp* ones." It also states the authentication prerequisite, so the agent knows a call is only meaningful for a logged-in user.

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.