Skip to main content
Glama

bx_profiles_list

Read-onlyIdempotent

Lists locally configured model profiles and their readiness status, so you can verify available models without exposing keys or making model calls.

Instructions

列出模型配置及就绪状态,不返回密钥。 / List locally configured model profiles and readiness. No key values or model call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
kindYes
productYes
api_versionYes
business_decisionYes
execution_authorizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0-rc.9-linux.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond those annotations: it returns no key values, and it performs no model call, which matters because 'readiness' could otherwise be read as an active probe. Return shape is left to the output schema, which is appropriate.

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

Conciseness5/5

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

Two short clauses per language, with the resource and the two exclusions (no keys, no model call) front-loaded. Every phrase carries information, and the bilingual mirroring does not add redundancy for an agent reading either line.

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

Completeness5/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 list tool with an output schema that documents return values, the description covers everything an agent needs: what is listed, that secrets are excluded, and that no model is invoked. Nothing essential is missing.

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 no parameters, so the baseline is 4. The empty schema with additionalProperties=false leaves nothing for the description to clarify, and the description correctly spends no words on parameter detail.

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 gives a specific verb+resource: list locally configured model profiles and their readiness state. It is clearly distinguishable from siblings such as bx_dictionaries_list or bx_projects_list because it names the exact resource domain (model profiles). It stops short of a 5 only because it never explicitly contrasts itself with any sibling tool.

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 by the resource: an agent enumerates profiles when it needs to know which models are configured and ready. There is no explicit when-to-use statement, no exclusions, and no pointer to an alternative tool for a related need. Adequate for a trivial zero-argument list call, but the guidance is inferred rather than stated.

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