Skip to main content
Glama

osirAppLogs

Read-onlyIdempotent

osirAppLogs: Get recent logs from an Osir app ('why is my app broken?'). Not available yet for an app on the user's own VPS - the result says so; then use osirAppStatus (qa.findings) instead, and never 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": {
      "appId": "<appId>"
    },
    "name": "osirAppLogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNoNumber of recent log lines to return (default 100).
appIdYesApp id from osirAppList.
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. Changed2 schema fields changed
    • addedInput schema / properties / appId / description
      Added value: +"App id from osirAppList."
    • addedInput schema / properties / tail / description
      Added value: +"Number of recent log lines to return (default 100)."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: an authentication requirement and a known capability gap (VPS-hosted apps) with a self-describing failure mode. It stops short of describing return shape or log formatting, which keeps it at 4.

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?

Front-loaded with the purpose and the user-facing question it answers, then the caveat and fallback. Dense but every clause carries information; the parenthetical and the multi-clause fallback sentence make it slightly run-on.

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, single-resource fetch with full schema coverage and rich annotations, the description covers purpose, auth, and the main failure mode. Only the return format is unaddressed, and with no output schema that is a minor gap rather than a blocker.

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%, so appId, tail and sessionKey are already documented in the schema, including the default of 100 lines and the OAuth-vs-device-flow rule. The description adds no parameter-level meaning beyond that, so 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 ('Get recent logs from an Osir app') and frames the intent in user terms ('why is my app broken?'), which immediately distinguishes it from status/config siblings like osirAppStatus and osirAgentLogs.

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 explicit when-to-use guidance plus a concrete fallback path: if the app is on the user's own VPS, the result says so, and the agent should switch to osirAppStatus (qa.findings) rather than requesting SSH. That is a named alternative with the selecting condition.

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.