Skip to main content
Glama

my_changes

Read-onlyIdempotent

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). List your own changes, their games, versions and status. Optionally filter by game slug.

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": "my_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNo

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, and closed-world, so the safety profile is covered. The description adds genuinely non-structured context: an authentication prerequisite with two concrete mechanisms (OAuth connection or an Authorization: Bearer API key header). It does not mention result limits or pagination, which is the remaining behavioral gap for a listing tool.

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?

Three short sentences with no filler, and the auth prerequisite is placed up front so an agent hits the failure mode before attempting a call. Slightly better structure would lead with the core action and place auth as a secondary note.

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?

This is a simple one-parameter read with full annotation coverage and no output schema, and the description covers action, scope, return fields, filter semantics, and auth. Only pagination or result-size expectations are missing, a minor gap for a listing endpoint.

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?

Schema coverage is 0% and the single `game` property is an undescribed string, so the description carries the burden. "Optionally filter by game slug" successfully conveys both optionality and the expected value format (a slug, not an ID or display name), which is real meaning the schema lacks.

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?

"List your own changes, their games, versions and status" gives a specific verb and resource plus the returned fields, and "your own" signals the personal scope that likely separates it from workspace-wide siblings. It stops short of explicitly naming a sibling (e.g. my_games) to contrast with, so the differentiation is inferred rather than stated.

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?

The description notes the filter is optional, which implies the default no-argument behavior is a full personal listing. It offers no when-to-use versus alternatives guidance, no exclusions, and no indication of when the game filter is preferable to browsing via another tool.

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.

Resources