Skip to main content
Glama
Sign In

RTOpacks

by au.com.rtopacks
OverviewDiscussionsAdmin

RTO profile

rto_profile
Read-onlyIdempotent

The full register profile of a training organisation by its RTO code. Requires an RTOpacks subscription.

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": {
      "rto_code": "<rto_code>"
    },
    "name": "rto_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rto_codeYesThe training organisation's RTO code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds a meaningful access precondition (RTOpacks subscription) and indicates the response is the full register profile, though it does not describe failure or partial-access behavior.

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 short sentences, no repetition, with the core resource and access requirement front-loaded. Every phrase contributes.

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 one-parameter read-only lookup with rich annotations, the definition supplies the essential purpose and subscription prerequisite. It could be stronger with invalid-code or return-scope details, but it is adequate for correct invocation.

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% and the single rto_code parameter is documented in the schema; the description only restates that lookup is by RTO code. No extra format, validation, or example meaning is added.

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?

States the resource (full register profile of a training organisation) and the lookup key (RTO code), so the operation is identifiable. It does not explicitly distinguish itself from sibling register_search, but the 'full profile by code' framing is reasonably specific.

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?

Implies use when you already have an RTO code and need the full profile, and notes the RTOpacks subscription prerequisite. It gives no explicit when-not guidance or comparison to register_search/list_topics.

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

All RTOpacks 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