Skip to main content
Glama

osirAgentStatus

Read-onlyIdempotent

osirAgentStatus: Is the user's AI agent (e.g. Hermes) installed and working? Reports install progress, the dashboard URL, and whether the dashboard asks for a login (dashboardProtected - checked live). If an install failed, the message says why and what to do. Requires authentication.

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": {
      "agentId": "<agentId>"
    },
    "name": "osirAgentStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesAgent id from osirAgentList or osirAgentDeploy.
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.6/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive operation, and the description adds real context beyond that: the dashboardProtected value is checked live (not cached), failures return a reason plus remediation guidance, and authentication is required. The only missing behavioral detail is whether the status is eventually consistent right after a deploy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The content is relevant and the live-check and failure-message notes are front-loaded, but the leading "osirAgentStatus:" simply repeats the tool name, and the question-plus-clause construction is looser than a direct verb statement would be.

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?

There is no output schema, so the description carries the burden of explaining returns, and it does name the key fields (install progress, dashboard URL, dashboardProtected) as well as the failure-message content. An agent could call this correctly and interpret the response, though the success-state shape is still only sketched.

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 description coverage is 100%, with agentId and sessionKey both fully documented in the schema itself, including where the agent id comes from and when to include or omit the session key. The description adds nothing further about parameters, so the baseline of 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?

The description states a concrete resource and question ("Is the user's AI agent installed and working?") and enumerates the specific things it reports: install progress, dashboard URL, and dashboardProtected. It implicitly separates itself from siblings like osirAgentList and osirAgentDeploy by focusing on post-install health, but it never names an alternative explicitly.

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?

Usage is only implied: an agent can infer you call this to verify installation or diagnose a failed install, and the failure-message behavior hints at a troubleshooting role. There is no explicit statement of when to call it versus osirAgentList, osirAgentLogs, or osirAgentConfigure, and no guidance on polling frequency after a deploy.

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.