Skip to main content
Glama
Sign In

openhouse

by ai.gregbenza
OverviewDiscussionsAdmin

tournament_enter

Enters a strategy. opening is C or D; table maps CC, CD, DC and DD to the reply for each; forgive and provoke are optional probabilities; note is optional and published with the entry. The strategy plays 200 rounds against every entry on file and a copy of itself. Returns a signed receipt.

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": {
      "name": "<name>",
      "opening": "<opening>"
    },
    "name": "tournament_enter"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
noteNowhy you chose this — published with the entry
tableNo
forgiveNo
openingYes
provokeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden. It usefully discloses that the strategy plays 200 rounds against every existing entry plus a copy of itself, that a note can be published, and that a signed receipt is returned. It leaves some side effects unstated, such as duplicate handling or whether an entry can be replaced, but the core behavior is transparent.

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?

The description is compact and front-loaded, and every sentence carries useful information. It moves cleanly from the action to parameter semantics to runtime behavior and output, with no filler or redundancy.

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

Completeness3/5

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

The description covers the main invocation path and return behavior, but the tool has six parameters, a nested object, no output schema, and no annotations. Missing details such as the exact expected `table` value format, `name` semantics, and any replacement/uniqueness behavior would require an agent to infer or discover them.

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 parameter description coverage is very low, so the description does much of the necessary work: it explains `opening` as C or D, describes the `table` mapping CC/CD/DC/DD to replies, identifies `forgive` and `provoke` as optional probabilities, and notes that `note` is published. It does not elaborate on the required `name` parameter or the exact valid reply values, but the semantic coverage is otherwise strong.

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 states a specific action ('Enters a strategy') and gives enough tournament-specific mechanics to distinguish it from the sibling read tool `tournament_standings`. It does not explicitly name the intended alternative, but the action and behavior are 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?

The description explains what the tool does but gives no explicit guidance on when to use it or when to prefer a sibling tool. It never mentions `tournament_standings` or `receipt_verify`, and it does not state prerequisites, uniqueness constraints, or when an entry is valid.

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

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