Skip to main content
Glama

Create a scoreboard

create_scoreboard
Idempotent

Create a public, shareable two-team scoreboard at zero. Requires explicit user intent to create; title and team names are public. Works without signing in: the result then includes a private claim.url (valid up to seven days) for the person who will keep score; it lets them score in the browser and keep the board. Share links.spectator with viewers. A board made without a connection cannot be updated by later tool calls; connect an account first if you need to keep score. Free boards allow 50 total spectator views and show branding. With a connection, retry the identical requestId and input after a timeout; without one, a retry creates another board.

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": {
      "requestId": "<requestId>",
      "title": "<title>",
      "teams": "<teams>"
    },
    "name": "create_scoreboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamsYes
titleYes
requestIdYes

Output Schema

NameRequiredDescriptionDefault
idYes
claimNo
linksYes
teamsYes
titleYes
limitsYes
revisionYes
connectionNo
capabilitiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / claim
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "expiresAt": {
      +      "type": "number"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "url",
      +    "expiresAt"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / connection
      Added value: +{
      +  "const": "guest",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses external side effects and lifecycle details: public visibility of title and team names, a claim.url valid up to seven days, spectator share links, a 50-view free-tier cap with branding, and the crucial limitation that an anonymously created board cannot be updated by later tool calls. It also explains conditional idempotency (identical requestId after timeout only dedupes when connected), which meaningfully contextualizes the idempotentHint annotation rather than contradicting it.

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?

Purpose and the intent gate are front-loaded, and nearly every sentence adds actionable information (auth, retention, quota, retry). Some phrasing is garbled and wasteful, notably the fragment 'Share links.spectator with viewers.', which is not proper English and briefly obscures the share-link behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is an open-world, side-effecting creation tool with an output schema, and the description covers everything an agent needs to decide and act: consent requirement, anonymous vs connected consequences, quota limits, credential retention window, and retry semantics. Return-value details are left to the output schema, as appropriate.

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 description coverage is 0%, so the description must carry parameter meaning, and it largely does: it states the two-team shape of 'teams', that title and team names become public, and that requestId is a retry key for identical requests after a timeout. It omits the title length bound (1-100) and the requestId pattern, which the schema constrains but never explains.

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?

The description opens with a specific verb and resource ('Create a public, shareable two-team scoreboard') and adds distinguishing traits (two teams, public, shareable) that separate it from get_scoreboard, update_scoreboard, and hand_off_scoreboard. An agent can identify the operation without opening the 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?

It gives a real gating condition ('Requires explicit user intent to create') and conditional guidance on anonymous vs connected usage ('connect an account first if you need to keep score'). It stops short of naming sibling tools (e.g. 'use update_scoreboard to change an existing board'), so routing between siblings is only implied.

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.