Skip to main content
Glama
Sign In

tollbooth

by io.github.huwhitememes
OverviewDiscussionsAdmin

openrouter_models

OpenRouter model catalog — id, name, context_length, pricing, created. Cached 1h, auto-fetched via public API. For model routing decisions.

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": "openrouter_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax models to return, default 100
min_contextNoMin context length filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With empty annotations, the description carries full behavioral disclosure burden. It adds caching behavior ('Cached 1h') and data source ('auto-fetched via public API'), which are valuable beyond bare minimum. No destructive actions are indicated, and no contradictions exist.

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 three concise sentences: first lists contents, second covers caching and source, third states purpose. No redundant words, front-loaded with key information. Every sentence earns its place.

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 simple listing tool with two optional parameters and no output schema, the description covers caching, data source, and purpose. It does not detail output format or pagination, but given the low complexity and high schema coverage, it is nearly complete. A 4 is reasonable.

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 description coverage is 100%, so the schema already documents the two parameters (limit, min_context). The description adds overall context but does not enhance parameter meaning beyond what the schema provides. Baseline 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 lists models from OpenRouter with specific fields (id, name, context_length, pricing, created). It distinguishes itself from diverse sibling tools by focusing on the model catalog, making its purpose 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?

The description mentions 'For model routing decisions' which implies context but does not provide explicit when-to-use or when-not-to-use guidance, nor does it compare with alternatives like model_settings_lookup. Usage is implied but not fully clarified.

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

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