Skip to main content
Glama

Voicedex

get_model

Read-onlyIdempotent

One model's record: pricing with all variants (e.g. streaming vs pre-recorded) and source, languages, capabilities with notes (e.g. "pre-recorded only, English only"), regions, interfaces, audio formats, limits, lifecycle, shutdown date and replacement, open-weights licence, provenance. model: key or loose name. detail="compact" (default) groups regional language codes and trims source URLs; "full" returns everything.

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": {
      "model": "<model>"
    },
    "name": "get_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
detailNocompact

Output Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond that: what the record contains, the default detail level, and specifically how "compact" transforms output (grouping regional language codes, trimming source URLs) versus "full" returning everything.

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?

The first sentence is a dense field enumeration that front-loads what the agent gets back, and the detail-level behavior is placed last where it belongs. The long comma-list verges on run-on, but nearly every item is substantive rather than 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?

For a two-parameter read tool with an output schema, the definition covers the model identifier, the detail default, and the transformation compact applies. An output schema exists, so the field enumeration is partly redundant, but the remaining gap is minor: no guidance on lookup failure or ambiguous names.

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?

With 0% schema description coverage, the description carries the parameter burden and does add meaning: "model" accepts a key or a loose name, and "detail" is explained functionally rather than just by enum values. However, the fuzzy "loose name" matching behavior is not elaborated (ambiguity resolution, failure mode), so the compensation is partial rather than complete.

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-and-resource framing ("One model's record") and enumerates the record's contents, so an agent knows this is a single-model lookup rather than a search. It does not explicitly name how it differs from siblings like search_models, but the singular scope makes the distinction inferable.

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 implied rather than stated: fetching the full record for a single model whose key or name you already have. There is no explicit when-not guidance or pointer to search_models/compare_models for discovery, and no statement about what happens if the name doesn't resolve.

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.