Skip to main content
Glama

Oneview Rest Get

oneview_rest_get
Read-onlyIdempotent

Retrieve read-only OneView REST resources not covered by other tools, including networks, uplink sets, logical enclosures, tasks, and utilization data; secrets are redacted.

Instructions

Raw read-only GET of any OneView REST resource, for data the other oneview_ tools don't cover (networks, uplink sets, logical enclosures, tasks, utilization). Secrets are redacted.

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": {
      "path": "<path>"
    },
    "name": "oneview_rest_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesOneView REST path starting with /rest/, e.g. /rest/logical-interconnects or /rest/server-hardware/{id}/utilization
applianceNoOneView appliance name from list_servers; omit to use the first one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact — "Secrets are redacted" — which matters for interpreting output, but says nothing about pagination, collection size limits, or what happens on an invalid path. A 3 reflects modest added value above the annotations.

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?

Two tight sentences with zero filler; the capability and the disambiguating scope constraint are both front-loaded. Nothing repeats structured fields verbatim or wastes the agent's attention.

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?

An output schema exists so return values need no explanation, and annotations cover safety. The remaining gap is operational: no note on collection pagination or on how errors surface for a malformed path, which matters for a generic raw-GET tool.

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 both parameters are already documented with examples and the appliance default is spelled out. The description adds only that any path is acceptable, which the schema already conveys via its /rest/ example format. 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 ("Raw read-only GET of any OneView REST resource") and immediately scopes it to data the other oneview_ tools don't cover, with concrete example resources (networks, uplink sets, logical enclosures, tasks, utilization). An agent can distinguish this escape-hatch tool from the typed siblings without opening either schema.

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

Usage Guidelines4/5

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

Explicitly frames this as the fallback when "the other oneview_ tools don't cover" the needed data, which is actionable when-to-use guidance. It stops short of naming which sibling to prefer for the covered resources or when-not to use this tool (e.g. for anything a typed tool already returns).

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