Skip to main content
Glama
Sign In
Nanites

Nanites

by ADn-001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Profiles

list_profiles

List available profile names to identify configured delegation models. Use verbose to retrieve full profile objects with details.

Instructions

List profile names. Pass verbose for full profile objects.

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

Input Schema

NameRequiredDescriptionDefault
verboseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It doesn't explicitly state that this is a read-only operation, nor does it disclose any side effects, return format, or pagination. However, as a list operation, the absence of any mutation hints is neutral, and the description does reveal that verbose changes the output detail.

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 sentences with no filler. The primary action and the parameter effect are front-loaded. Every word earns its place.

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 list tool with one optional parameter and no output schema, the description covers the essential behavior: what it lists and how the flag alters the output. It lacks details like error conditions or ordering, but these are minor for this simple operation. The description is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides only a boolean 'verbose' parameter with no description (0% schema coverage). The description fully compensates by explaining that passing verbose yields full profile objects, while default behavior lists profile names. This is exactly the kind of clarification an agent needs.

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?

The description clearly states a specific action ('List') on a specific resource ('profile names'), and distinguishes it from sibling tools like create_profile, switch_profile, and get_active_profile. The phrase 'profile names' vs 'full profile objects' also hints at a scoping detail that sets it apart.

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?

The description implies when to use it (to list profiles) but provides no explicit exclusions or alternatives. It doesn't say 'use this when you need to enumerate all profiles' or mention any sibling for comparison. For a simple list tool, the usage is fairly obvious, but it lacks explicit guidance.

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