Skip to main content
Glama
modelanalyzer-mcp

modelanalyzer-mcp

by yeaske

List use-case scenarios

list_scenarios
Read-only

Lists the use-case scenarios, such as coding assistant, support bot, or bulk classification, that model recommendations are ranked for, so you can pick the right scenario to query.

Instructions

List the use-case scenarios (coding assistant, customer support bot, bulk classification, ...) that recommend_models ranks for.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds only that the returned scenarios are the ones recommend_models ranks for, which is useful context; it says nothing about whether the list is static or dynamic, or how values should be passed onward.

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 well-formed sentence with the resource front-loaded and the sibling relationship trailing as a qualifier. No filler, though the trailing "that recommend_models ranks for" slightly buries the most actionable detail.

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 zero-parameter, read-only enumeration tool with no output schema, this covers what the tool returns and why it exists. The only gap is not stating explicitly that the returned scenario identifiers are the accepted input values for recommend_models.

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 there is nothing for the description to disambiguate. Baseline 4 applies; the enumerations in the parenthetical incidentally signal the shape of returned values.

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?

Specific verb ("List") plus a concrete resource ("use-case scenarios"), and the parenthetical examples (coding assistant, customer support bot, bulk classification) make the resource unambiguous. It also ties itself to the sibling recommend_models, so an agent can distinguish it from the ranking tool without opening a schema.

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: by naming recommend_models as the consumer of these scenarios, it hints that this is the discovery step before recommending. There is no explicit "call this first when..." instruction and no when-not-to-use guidance or named alternatives.

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