Skip to main content
Glama
Sign In
agent-bridge

agent-bridge

by avas-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scenario.list

scenario_list

Lists available app-defined scenarios, such as a signed-in user, with name, description, JSON Schema options, and active status so agents can choose the correct setup.

Instructions

Setups the app defines, e.g. a signed-in user: name, description, options (a JSON Schema), active.

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

Input Schema

NameRequiredDescriptionDefault
argsNoThe tool's arguments, in order (each any JSON value). Leave out for none.
fullNoReturn a result over 32 KB whole instead of a summary of its size and shape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that returned setups include name, description, options (JSON Schema), and active, which is useful return-shape information. However, it does not explicitly state that the operation is read-only, whether it returns all setups, or how the summary-vs-full behavior works.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the domain object, but it is an incomplete sentence fragment and the colon-list structure is slightly cryptic. It avoids waste but does not provide a clean, well-structured sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter list tool with no output schema and no annotations, the description supplies the returned item fields, which partly compensates for the missing output schema. It does not explain the 'full' parameter's effect on output or clarify that the tool enumerates all setups, leaving notable gaps.

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 the meanings of args and full are already documented in the input schema. The description adds no extra parameter guidance beyond saying options is a JSON Schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names the resource ('setups the app defines') and lists example fields, but never states the action (list/return) explicitly. The tool name supplies 'list', but the description alone is a noun phrase rather than a clear verb+resource statement, and it does not distinguish from scenario_apply or scenario_restore.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no comparison to siblings such as scenario_apply or scenario_restore. The agent must infer that this is the read-only enumeration tool from the name alone.

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

Deploy Server

Other Tools