Skip to main content
Glama

Good Turn Studio (all tools)

by io.github.GoodTurnStudio
OverviewDiscussionsAdmin

Form Guide: Two clubs side by side before they meet

formguide_compare_teams
Read-onlyIdempotent

Form Guide. Two clubs side by side before they meet. For requests like "Arsenal v Leeds, how do they compare?". Gives positions, form, goals, this season's meeting and the next date they play. Stats only, not betting advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
awayYesA different club from home.
homeYesThe home club, for example Arsenal.
team1NoOlder name for home, kept for existing callers; home is the current name.
team2NoOlder name for away, kept for existing callers; away is the current name.
countryNoUS or CA adds US Eastern kick-off times to the say line (and to each fixture's us_eastern, which is always there when a time is known).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Pass US or CA to add US Eastern kick-off times to the say line (and to each fixture's us_eastern, which is always there when a time is known)."New value: +"US or CA adds US Eastern kick-off times to the say line (and to each fixture's us_eastern, which is always there when a time is known)."
    • changedInput schema / properties / team1 / description
      Previous value: -"Older name for home, kept for existing callers. Use home."New value: +"Older name for home, kept for existing callers; home is the current name."
    • changedInput schema / properties / team2 / description
      Previous value: -"Older name for away, kept for existing callers. Use away."New value: +"Older name for away, kept for existing callers; away is the current name."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds real value beyond that: it enumerates the returned stats and scopes the tool explicitly ('Stats only, not betting advice'), which prevents an agent from misusing it as a prediction/advice source.

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, front-loaded with the purpose, then an example, then the output/scope. The leading 'Form Guide.' is slightly redundant with the title but the rest earns its place with no padding.

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?

There is no output schema, and the description compensates by listing the fields returned and clarifying scope. With a fully documented 5-parameter schema and full annotation coverage, the only missing piece is explicit routing among the other formguide_* tools.

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 description coverage is 100%, and each parameter (home, away, team1, team2, country) is documented in the schema itself, including the legacy-alias behavior of team1/team2 and the country effect on US Eastern times. The description adds no parameter-level meaning beyond this, so the baseline 3 applies.

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 a specific verb (compare) and resource (two clubs), and enumerates the output ('positions, form, goals, this season's meeting and the next date they play'). It implicitly contrasts with formguide_get_team by emphasizing 'two clubs side by side', but never names that sibling, so an agent must infer the boundary rather than read it.

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?

Provides a concrete trigger utterance ('Arsenal v Leeds, how do they compare?') plus a temporal cue ('before they meet'), which gives clear context for when to reach for this tool. It stops short of stating when NOT to use it or which sibling handles single-team or table queries instead.

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

All Good Turn Studio (all tools) 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