Skip to main content
Glama
Sign In

Besidka

by com.besidka
OverviewDiscussionsAdmin

List models

list_models
Read-onlyIdempotent

List the models Besidka offers with provider, context window, price per million tokens (price.tokens is the token unit for price.input and price.output), price tier, input and output modalities, tools, tool calling and reasoning support. Deprecated models are hidden unless includeDeprecated is true.

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

Input Schema

NameRequiredDescriptionDefault
providerNoOnly list models of this provider id
includeDeprecatedNoAlso list deprecated models. Defaults to false

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 establish readOnly/idempotent behavior, but the description adds what is actually returned (provider, context window, price tier, modalities, tool-calling and reasoning support) and how price fields are keyed (price.tokens as the unit for price.input and price.output). The default-hiding of deprecated models is also disclosed, which is real behavioral information not present in annotations.

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, front-loaded with the action and the returned fields; the parenthetical clarifying price.tokens earns its space given the ambiguity of the field name. Dense but no filler.

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?

There is no output schema, so the description must carry the return shape, and it does by enumerating the fields each model entry contains. A minor gap is that nothing is said about ordering, pagination, or result size, though for a small fixed catalog this is low-risk.

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%, so both parameters are already documented in the schema. The description restates includeDeprecated's effect and adds no syntax or edge-case detail for provider; the added meaning about price.tokens concerns return values rather than parameters. Baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('List the models Besidka offers') and enumerates the attributes each entry carries (provider, context window, price, modalities, tools, reasoning). An agent can distinguish it from list_providers, which is about providers rather than models, though the sibling is not named.

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 deprecated-model rule ('hidden unless includeDeprecated is true') gives a concrete usage condition and the schema mirrors it. There is no explicit guidance on when to call this versus list_providers, so selection between the two catalog tools is left to inference.

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

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