Skip to main content
Glama
Sign In

Forge Engine

by app.forgeengine
OverviewDiscussionsAdmin

propose_balance_table

Propose a stat-doc TABLE → Inbox. csv (header; key% = percent; first column = name) OR schema+rows. Adopting REPLACES same-named.

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": {
      "title": "<title>"
    },
    "name": "propose_balance_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNoHeader + rows; non-numeric = info
rowsNo[{name, atk: 350, …}]
titleYesTable name
schemaNo[{key, mode: flat|pct|text, base, min, max, desc}]
registryNotrue = the shared Stats registry
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / csv / description
      Previous value: -"CSV text: header row + data rows. `atk` = flat value, `atk%` = percent value, non-numeric columns become info."New value: +"Header + rows; non-numeric = info"
    • removedInput schema / properties / project_id / description
      Removed value: -"Project id (from list_projects) to act on; omit = the connector URL's project."
    • changedInput schema / properties / registry / description
      Previous value: -"true = this is the shared Stats registry (rows are stat definitions)."New value: +"true = the shared Stats registry"
    • changedInput schema / properties / rows / description
      Previous value: -"Row values [{name: \"blade\", atk: 350, …}] (with `schema`)."New value: +"[{name, atk: 350, …}]"
    • changedInput schema / properties / schema / description
      Previous value: -"Column definitions [{key, mode: flat|pct|text, base, min, max, desc}] (alternative to csv). A `name` text column is guaranteed."New value: +"[{key, mode: flat|pct|text, base, min, max, desc}]"
    • changedInput schema / properties / title / description
      Previous value: -"Table name (e.g. \"Weapons\")"New value: +"Table name"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses key behavioral traits: proposals go to Inbox, and adopting REPLACES same-named tables. Annotations only include destructiveHint:false, so this adds meaningful context beyond the structured data.

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 two compact sentences, front-loaded with the main purpose. Every clause adds value: table type, inbox destination, input options, and replacement behavior.

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 proposal tool with 6 params and no output schema, the description covers the core purpose, input formats, and adoption consequence. It omits project_id and registry details, but those are likely standard context parameters shared across sibling tools.

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 high (83%), but the description adds important format details: csv header requirements, percent notation, first column as name, and the schema+rows combination. This goes beyond the schema descriptions.

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 clearly states the verb 'Propose', the resource 'stat-doc TABLE', and the target 'Inbox'. It distinguishes from sibling tools like propose_balance_board by specifying TABLE, making it unambiguous.

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?

Usage is implied by the resource type (table vs. board) but no explicit alternatives or exclusions are mentioned. The description does not say when to use this tool instead of propose_balance_board or other propose_* tools.

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

All Forge Engine 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