Skip to main content
Glama
Sign In

Compute Screener

by com.computescreener
OverviewDiscussionsAdmin

Read a Compute Screener page

fetch
Read-onlyIdempotent

The full text of a result from search, by its id (gpu:H100, company:OpenAI, model:, provider:, page:methodology, page:futures, page:verification, page:power, page:coding, page:datacenters) or the page's address: prices, changes, history, providers or models, as on the site.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id from search, or a page's address (https://computescreener.com/gpu/h100).

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search."New value: +"An id from search, or a page's address (https://computescreener.com/gpu/h100)."
  2. Changed5 schema fields changed
    • changedOutput schema / properties / id / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / metadata / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / text / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / title / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds that it returns full text and enumerates accepted id/page forms, but does not cover rate limits, auth needs, or pagination details. No annotation contradiction is present.

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?

A single dense sentence that front-loads the return content and enumerates accepted forms without filler. The long parenthetical list earns its place by documenting valid ids, though the sentence could be slightly easier to parse.

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 one-parameter read tool with rich annotations and an output schema, the description covers the key input forms and return content. Nothing critical is missing for correct invocation.

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 100% and the schema provides an example URL, but the description adds substantial value by enumerating id prefixes (gpu:, company:, model:, provider:, page:) and valid page names such as prices, changes, history, providers, and models. This meaningfully clarifies the single parameter beyond the schema.

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 that the tool returns the full text of a search result or a named page by id/address, clearly distinguishing it from the sibling search tool by implying retrieval of full content. The noun-phrase construction and vague phrase 'as on the site' keep it from a perfect 5, but the resource and operation 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the id comes from search and lists accepted page addresses, giving some usage context. However, it does not explicitly say when to use this tool versus sibling get_* tools, nor does it provide any when-not guidance.

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

All Compute Screener 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