Skip to main content
Glama
Sign In
scdo-agent-plugins

scdo-agent-plugins

by SCDOLAB
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Games catalog

games_catalog
Read-only

Retrieve SCDO games with play links, including free demos and SCDO points bookkeeping titles, to help users find and launch games on scdo.com.au.

Instructions

SCDO Games list with play links on scdo.com.au (free demo and SCDO points bookkeeping games).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "games_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine content context beyond that (hosted on scdo.com.au, free demo and SCDO points bookkeeping games), but says nothing about the shape of the returned list or whether the play links are external URLs.

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?

A single compact sentence with no filler, and the identifying information is front-loaded. The parenthetical is dense but earns its place by characterizing the game types.

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 no-argument, read-only listing tool with annotations covering safety and no output schema, the description supplies enough to call it correctly. Only the return structure remains unspecified, which is a minor gap at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate in the schema, and it does not need to.

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 names a specific resource (SCDO Games list) and says what it contains (play links), which lets an agent distinguish it from the catalog-like siblings such as x402_catalog and wallet_downloads. The verb is implicit ('list') rather than stated, but the purpose is clear.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the other catalog/listing siblings, and no prerequisites or exclusions. The agent must infer usage entirely from the name and content hint.

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

Deploy Server

Other Tools