Skip to main content
Glama

Estimate FPS

estimate_fps
Read-onlyIdempotent

Average FPS of a graphics card (optionally with a specific CPU) at 1080p, 1440p and 4K in games measured by published benchmarks (ComputerBase, HWBen) or estimated from official requirements. Also says whether the CPU or GPU limits performance.

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": {
      "gpu": "<gpu>"
    },
    "name": "estimate_fps"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpuNoProcessor slug or name; defaults to a Ryzen 7 9800X3D reference
gpuYesGraphics card slug or name, e.g. 'RTX 4060'
gameNoGame slug or name from list_games; omit for all measured games
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, closed-world), so the description's contribution is provenance: results come either from published benchmarks (ComputerBase, HWBench) or are estimated from official requirements, which signals varying reliability the annotations cannot convey. It also discloses that the response includes a bottleneck verdict, extra information beyond the stated inputs. It does not say what happens when no benchmark or requirement data exists, which is the remaining gap.

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?

Two sentences with no filler, front-loaded with the primary output (average FPS) and then the secondary output (bottleneck verdict). The parenthetical qualifier and source list are dense but each earns its place; slight crowding of provenance detail into the main sentence keeps it from a 5.

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?

With no output schema, the description does the needed work of indicating what comes back: FPS across 1080p, 1440p, and 4K plus a CPU/GPU limiter verdict. For a four-parameter read-only tool that is close to sufficient; only the empty-data case and result granularity (per game vs aggregate) are left unstated.

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 coverage is 75% and the schema already documents gpu, cpu (including the Ryzen 7 9800X3D default), and game via list_games. The description adds only the optionality of cpu and the set of resolutions, both of which the schema already encodes through a default note and an enum. Baseline 3 is appropriate when structured fields carry most of the meaning.

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 concrete resource and metric: average FPS for a graphics card, optionally paired with a CPU, at three named resolutions. It also reveals the return signal (CPU-vs-GPU bottleneck), so an agent knows exactly what question this tool answers. It stops short of naming a sibling such as check_build to differentiate itself, which keeps it at 4 rather than 5.

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 only implied: the framing ('in games measured by published benchmarks ... or estimated from official requirements') tells the agent this is the performance-lookup tool, but there is no explicit when-to-use statement, no exclusion, and no pointer to an alternative for build-level or price-level questions. The reader must infer the boundary against check_build and get_model_prices.

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