Skip to main content
Glama

osirAgentLogs

Read-onlyIdempotent

osirAgentLogs: Logs of the user's AI agent (e.g. Hermes). Not available yet - the result says so; then use osirAgentStatus. Never invent log contents or ask the user for SSH access. 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": "osirAgentLogs"
  }
}

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

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description only needs to add context. It does: it discloses that the capability is not yet available, how that surfaces (in the result), and the required authentication. What it omits is anything about log format, volume, or pagination, so it stops short of the full behavioral picture.

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?

Three short sentences, front-loaded with the resource and immediately followed by the unavailability caveat and the fallback. The prefix 'osirAgentLogs:' repeats the tool name, but every other clause carries actionable information.

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 two-parameter read tool with a fully described schema, no output schema and annotations covering safety, the description supplies the missing pieces an agent needs: auth requirement, current unavailability, and the correct fallback. Return shape is left implicit, which is the only notable 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%, so agentId and sessionKey are already fully documented in the schema, including where each value comes from. The description adds no syntax, format, or conditional guidance beyond that, which is the expected baseline when the schema does the work.

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 (logs of the user's AI agent, e.g. Hermes) and implies retrieval, which separates it from siblings like osirAgentStatus and osirAppLogs at a high level. It never explicitly contrasts itself with osirAppLogs, so sibling differentiation is only partial.

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?

It says exactly what to do when the tool cannot be used ('Not available yet - the result says so; then use osirAgentStatus'), naming the fallback sibling. It also sets explicit negative guidance ('Never invent log contents or ask the user for SSH access'), which pre-empts the most likely agent failure modes.

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.