Skip to main content
Glama
Sign In
VoidFeed

VoidFeed

Official
by voidfeedai-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

voidfeed_benchmark_lookup

Look up model benchmark scores with confidence intervals for 247 model-benchmark combinations.

Instructions

Look up model benchmark scores. Surface tier: 8 entries. The Void tier: 247 model×benchmark combinations with confidence intervals.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "voidfeed_benchmark_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel name to look up
benchmarkNoBenchmark name (e.g. MMLU, HumanEval, MATH)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description adds some context about benchmark scores including confidence intervals and specific entry counts (8 Surface, 247 Void), but it does not disclose read-only status, authentication needs, or data freshness.

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 concise with two sentences that front-load the purpose. Every word adds value, no 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?

With no output schema, the description mentions benchmark scores and confidence intervals but lacks details on output format, sorting, or pagination. It provides moderate completeness for a lookup tool.

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 100% with descriptive parameter names. The description does not add additional meaning beyond the schema's property descriptions, so baseline score of 3 is appropriate.

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 tool looks up model benchmark scores, mentioning specific tiers (Surface and Void) and counts, which differentiates it from siblings like voidfeed_model_compare (comparison) and voidfeed_catalog (catalog).

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?

The description implies usage for looking up scores but does not explicitly state when to use this tool instead of alternatives like voidfeed_model_compare or voidfeed_catalog. No exclusions or when-not-to-use guidance is provided.

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

Deploy Server

Other Tools