Skip to main content
Glama

list_embedding_models

Lists available embedding models and their details so you can select the appropriate one for running S3 bibliometric analysis.

Instructions

Embedding models the user can choose for run_s3_analysis (key, model, kind, max tokens, description). Default: mpnet, the model used in the published S3 paper.

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_embedding_models"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral fact an agent needs: there is a default (mpnet, the S3 paper model) and the tool returns a fixed set of model attributes, making the read-only, no-side-effect nature evident by construction. It does not explicitly state there are no side effects or that the list is static, which keeps it below a 5.

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 front-loaded sentence with no filler: resource, use site, returned fields and default all appear in order of importance. The parenthetical field run-on is slightly compressed but costs no clarity.

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?

An output schema exists, so return shape need not be explained, yet the description still names the fields; combined with the default value and the tie to run_s3_analysis, an agent has what it needs for a zero-param list. The missing piece is an explicit instruction to pass the returned key into run_s3_analysis.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The parenthetical field list describes return values rather than inputs, so it does not affect this dimension.

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?

The description identifies the exact resource (embedding models selectable for run_s3_analysis) and enumerates the returned fields (key, model, kind, max tokens, description). That is enough to distinguish it from the other list_* siblings, which cover communities, questions, runs and papers rather than models. The only weakness is the fragmentary phrasing with no explicit verb.

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: naming run_s3_analysis makes it clear this is a lookup to run beforehand to obtain a valid model key, and the default (mpnet) tells the agent it can skip the call if the default suffices. No explicit when-to-use/when-not-to-use sentence or mention of alternatives is given.

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