Skip to main content
Glama
Sign In

OTP

by io.github.david-steel
OverviewDiscussionsAdmin

Get an operating system file

get_oos
Read-only

Get a specific published OOS file by its ID, including organization metadata and file details.

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": {
      "id": "<id>"
    },
    "name": "get_oos"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe OOS file ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, non-destructive operation. The description adds useful return-content context ('including organization metadata and file details') and notes the file is 'published,' but it does not clarify permission requirements, error behavior, or whether unpublished files are inaccessible.

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?

The description is a single efficient sentence. It is front-loaded with the action and resource and includes the most important return-content note without any wasted words.

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 one-parameter read tool with no output schema, the description covers the core action and return contents. Minor gaps remain around how it differs from OOS browsing/comparison siblings and what happens for invalid or unpublished IDs.

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 the single ID parameter is already fully documented in the schema. The description's phrase 'by its ID' aligns with the schema but adds no format, source, or lookup guidance beyond it, making the baseline 3 appropriate.

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 specific verb and resource: 'Get a specific published OOS file by its ID.' The phrase 'specific published' implicitly distinguishes it from browsing or listing siblings, but it does not name an alternative such as browse_oos or compare_oos.

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 should call this when it already has an OOS file ID. There is no explicit guidance on when to use this versus browse_oos, compare_oos, or other OOS-related siblings, and no stated prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OTP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources